Packet flow control in a header of a packet

ABSTRACT

Techniques for controlling packet flows are described. In an example, a packet is sent on a virtual network. The packet&#39;s header includes scoping data that indicates a network boundary within which the packet is permitted and/or prohibited to flow. A network virtualization device of a substrate network receives the packet. The network virtualization device determines the scoping data from the header and, based on network configuration information, determines the forward flow of the packet. If the forward flow falls within a permitted network boundary indicated by the scoping data, the network virtualization device sends the packet forward. Otherwise, the packet is dropped.

BACKGROUND

A cloud infrastructure, such as Oracle Cloud Infrastructure (OCI), canprovide a set of cloud services that enable entities (e.g., enterprises)subscribing to these services to build and run a wide range ofapplications and services in a highly available cloud-hostedenvironment. The subscribing entities are referred to as customers ofthe cloud services provider. A cloud infrastructure can offerhigh-performance compute, storage, and network capabilities in aflexible overlay virtual network that runs on top of the physicalunderlay network and that is securely accessible from an enterprise'son-premises network. A cloud infrastructure, such as OCI, generallyallows customers to manage their cloud-based workloads in the same waythey manage their on-premises workloads. Thus, organizations can get allthe benefits of the cloud with the same control, isolation, security,and predictable performance as their on-premises network.

Virtual networking is a foundation for cloud infrastructures and cloudapplications because virtual networking enables the ability to access,connect, secure, and modify cloud resources. Virtual networking enablescommunication between multiple computers, virtual machines (VMs),virtual servers, or other devices across different physical locations.While physical networking connects computer systems through cabling andother hardware, virtual networking uses software management to connectcomputers and servers in different physical locations over the Internet.A virtual network uses virtualized versions of traditional networkcomponents, such as network switches, routers, and adapters, allowingfor more efficient routing and easier network configuration andreconfiguration.

BRIEF SUMMARY

The present disclosure relates generally to controlling packet flows. Inan example, a compute instance generates a packet to be sent on avirtual network. The packet's header includes scoping data thatindicates a network boundary within which the packet is permitted and/orprohibited to flow. A network virtualization device of a substratenetwork receives the packet. The network virtualization devicedetermines the scoping data from the header and, based on networkconfiguration information, determines the forward flow of the packet. Ifthe forward flow falls within a permitted network boundary indicated bythe scoping data, the network virtualization device sends the packetforward. Otherwise, the packet is dropped.

In an illustration, a compute instance is hosted within a first virtualcloud network (VCN) of a customer. Input of the customer may be receivedand may indicate that access to the compute instance is permitted toother compute instances within a peered second VCN and is prohibited toresources from an on-premise network of the customer. A packet flow rulecan be generated for the compute instance and stored for a virtualnetwork interface card (VNIC) hosted on a first network virtualizationdevice and associated with the compute instance. The compute instancegenerates a first packet that is destined to a compute instance of thesecond VCN. Upon receiving this first packet, the first networkvirtualization device identifies the packet flow rule, and generates andadds scoping data to the first packet, where this data permits the firstpacket to be sent to the second VCN but not the on-premise network. Thefirst network virtualization device sends the first packet (updated toinclude the scoping data) on a substrate network. A second networkvirtualization device, such as one hosting a dynamic routing gateway(DRG), receives the first packet from the substrate network anddetermines, based on the scoping data, that it can be sent to the secondVCN. Accordingly, the first packet is sent to the second VCN. Incomparison, the compute instance generates a second packet that isdestined to a resource of the on-premise network. Upon receiving thissecond packet, the first network virtualization device identifies thepacket flow rule, and generates and adds similar scoping data to thesecond packet, where this data permits the second packet to be sent tothe second VCN but not the on-premise network. Upon receiving the secondpacket, the second network virtualization device determines, based onthe scoping data, that it cannot be sent to the on-premise network.Accordingly, the second packet is dropped.

The terms and expressions that have been employed are used as terms ofdescription and not of limitation, and there is no intention in the useof such terms and expressions of excluding any equivalents of thefeatures shown and described or portions thereof. It is recognized,however, that various modifications are possible within the scope of thesystems and methods claimed. Thus, it should be understood that,although the present system and methods have been specifically disclosedby examples and optional features, modification and variation of theconcepts herein disclosed should be recognized by those skilled in theart, and that such modifications and variations are considered to bewithin the scope of the systems and methods as defined by the appendedclaims.

This summary is not intended to identify key or essential features ofthe claimed subject matter, nor is it intended to be used in isolationto determine the scope of the claimed subject matter. The subject mattershould be understood by reference to appropriate portions of the entirespecification of this disclosure, any or all drawings, and each claim.

The foregoing, together with other features and embodiments, will becomemore apparent upon referring to the following specification, claims, andaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative examples are described in detail below with reference tothe following figures.

FIG. 1 is a high level diagram of a distributed environment showing avirtual or overlay cloud network hosted by a cloud service providerinfrastructure according to certain embodiments.

FIG. 2 depicts a simplified architectural diagram of the physicalcomponents in the physical network within CSPI according to certainembodiments.

FIG. 3 shows an example arrangement within CSPI where a host machine isconnected to multiple network virtualization devices (NVDs) according tocertain embodiments.

FIG. 4 depicts connectivity between a host machine and an NVD forproviding I/O virtualization for supporting multitenancy according tocertain embodiments.

FIG. 5 depicts a simplified block diagram of a physical network providedby a CSPI according to certain embodiments.

FIG. 6 illustrates an example of network boundaries according to certainembodiments.

FIG. 7 illustrates an example of packet flow rules according to certainembodiments.

FIG. 8 illustrates an example of a packet structure that includesscoping data indicating a packet flow rule according to certainembodiments.

FIG. 9 illustrates an example of a method for controlling a packet flowaccording to certain embodiments.

FIG. 10 illustrates an example of a system for generating a packet flowrule according to certain embodiments.

FIG. 11 illustrates an example of a method for generating a packet flowrule according to certain embodiments.

FIG. 12 illustrates an example of a system for generating a packet thatincludes data indicating a packet flow rule according to certainembodiments.

FIG. 13 illustrates an example of a method for generating a packet thatincludes data indicating a packet flow according to certain embodiments.

FIG. 14 illustrates an example of a system for enforcing a packet flowrule indicated in scoping data of a packet according to certainembodiments.

FIG. 15 illustrates another example of a system for enforcing a packetflow rule indicated in scoping data of a packet according to certainembodiments.

FIG. 16 illustrates an example of a method for enforcing a packet flowrule indicated in scoping data of a packet information according tocertain embodiments.

FIG. 17 is a block diagram illustrating one pattern for implementing acloud infrastructure as a service system, according to at least oneembodiment.

FIG. 18 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 19 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 20 is a block diagram illustrating another pattern for implementinga cloud infrastructure as a service system, according to at least oneembodiment.

FIG. 21 is a block diagram illustrating an example computer system,according to at least one embodiment.

DETAILED DESCRIPTION

Techniques related to controlling packet flows are described. In anexample, a customer of a cloud infrastructure may operate a virtualnetwork, such as a virtual cloud network, hosted on the cloudinfrastructure. The flow of packets from and to a set of computeinstances can be controlled using various types of policies and rules.Commonly, security policies and routing rules can be implemented tocontrol the flow and can result in effective controls. Nonetheless,additional flow control improvements can be achieved as described in thepresent disclosure.

In an example, the customer may select a set of network boundarieswithin which the packet flow is permitted. Outside such boundaries, thepacket flow can be prohibited. For each of the compute instances of thecustomer's virtual network, a packet flow rule can be generated andstored, where this rule indicates the permissions and/or prohibitions ofthe compute instance's packet flows within the network boundaries giventhe customer's selection. When a compute instance generates and sends apacket addressed to a destination (egress or outbound traffic), thecorresponding packet flow rule is used to determine whether the flow ofthe packet falls within the permitted network boundary(ies). If not, thepacket is dropped. Otherwise, the packet can flow to the destinationalong a network path that can include a set of network virtualizationdevices and/or functions hosted thereat (e.g., routers, switches, loadbalancers, gateways, etc.). In this case, scoping data can be includedin the header of the packet to indicate the permitted networkboundary(ies) and is used to enforce the packet flow. In particular,each or a subset of the network virtualization devices or functions thatreceives and processes the packet can extract the scoping data from thepacket and then determine whether the packet can be sent forward orshould be dropped based on the permitted network boundary(ies) indicatedby the scoping data. Similarly, and for ingress or inbound traffic, whena packet is addressed to the compute instance, a network virtualizationdevice or a function hosted thereat can receive and process this packetto determine the scoping data and enforce the corresponding packet flowdepending on whether the compute instance belongs to a permitted networkboundary.

To illustrate, consider an example of a database of a customer hosted asa compute instance in a virtual cloud network of the customer. Thecustomer can indicate that access to the database is permitted within alayer-3 subnetwork of the virtual cloud network. Accordingly, when apacket is sent by the compute instance and includes database entries inits payload, scoping data can be added as metadata to a header of thepacket. This metadata can indicate that the scope is the layer-3 subnet.If a destination of the packet is within the layer-3 subnet, the packetflows to the destination. Otherwise, the packet is dropped before itreaches the destination. In another illustration, the customer indicatesthat the scope is permitted within a peered virtual cloud network butnot a public network. Here, the metadata indicates that the packet canbe sent to any compute instance hosted in the peered virtual cloudnetwork but cannot reach the public network. Accordingly, if the packetreaches a dynamic routing gateway on a remote peering connection, thedynamic routing gateway can send the packet onto the peered virtualcloud network. However, if an Internet gateway receives the packet, thisgateway drops the packet.

By using scoping data, several technological improvements can be made.For instance, a security policy or a routing rule may be configuredincorrectly (e.g., includes an error) or a software bug may exist thatcan compromise the security policy or routing rule. In such situations,the scoping data can provide another protection layer because itrepresents a way for the packet flow rule to travel with the packet anda way for enforcing this rule along one or more hops of the networkpath.

Example Virtual Networking Architectures

The term cloud service is generally used to refer to a service that ismade available by a cloud services provider (CSP) to users or customerson demand (e.g., via a subscription model) using systems andinfrastructure (cloud infrastructure) provided by the CSP. Typically,the servers and systems that make up the CSP's infrastructure areseparate from the customer's own on-premise servers and systems.Customers can thus avail themselves of cloud services provided by theCSP without having to purchase separate hardware and software resourcesfor the services. Cloud services are designed to provide a subscribingcustomer easy, scalable access to applications and computing resourceswithout the customer having to invest in procuring the infrastructurethat is used for providing the services.

There are several cloud service providers that offer various types ofcloud services. There are various different types or models of cloudservices including Software-as-a-Service (SaaS), Platform-as-a-Service(PaaS), Infrastructure-as-a-Service (IaaS), and others.

A customer can subscribe to one or more cloud services provided by aCSP. The customer can be any entity such as an individual, anorganization, an enterprise, and the like. When a customer subscribes toor registers for a service provided by a CSP, a tenancy or an account iscreated for that customer. The customer can then, via this account,access the subscribed-to one or more cloud resources associated with theaccount.

As noted above, infrastructure as a service (IaaS) is one particulartype of cloud computing service. In an IaaS model, the CSP providesinfrastructure (referred to as cloud services provider infrastructure orCSPI) that can be used by customers to build their own customizablenetworks and deploy customer resources. The customer's resources andnetworks are thus hosted in a distributed environment by infrastructureprovided by a CSP. This is different from traditional computing, wherethe customer's resources and networks are hosted by infrastructureprovided by the customer.

The CSPI may comprise interconnected high-performance compute resourcesincluding various host machines, memory resources, and network resourcesthat form a physical network, which is also referred to as a substratenetwork or an underlay network. The resources in CSPI may be spreadacross one or more data centers that may be geographically spread acrossone or more geographical regions. Virtualization software may beexecuted by these physical resources to provide a virtualizeddistributed environment. The virtualization creates an overlay network(also known as a software-based network, a software-defined network, ora virtual network) over the physical network. The CSPI physical networkprovides the underlying basis for creating one or more overlay orvirtual networks on top of the physical network. The virtual or overlaynetworks can include one or more virtual cloud networks (VCNs). Thevirtual networks are implemented using software virtualizationtechnologies (e.g., hypervisors, functions performed by networkvirtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR)switches, smart TORs that implement one or more functions performed byan NVD, and other mechanisms) to create layers of network abstractionthat can be run on top of the physical network. Virtual networks cantake on many forms, including peer-to-peer networks, IP networks, andothers. Virtual networks are typically either Layer-3 IP networks orLayer-2 VLANs. This method of virtual or overlay networking is oftenreferred to as virtual or overlay Layer-3 networking. Examples ofprotocols developed for virtual networks include IP-in-IP (or GenericRouting Encapsulation (GRE)), Virtual Extensible LAN (VXLAN—IETF RFC7348), Virtual Private Networks (VPNs) (e.g., MPLS Layer-3 VirtualPrivate Networks (RFC 4364)), VMware's NSX, GENEVE (Generic NetworkVirtualization Encapsulation), and others.

For IaaS, the infrastructure (CSPI) provided by a CSP can be configuredto provide virtualized computing resources over a public network (e.g.,the Internet). In an IaaS model, a cloud computing services provider canhost the infrastructure components (e.g., servers, storage devices,network nodes (e.g., hardware), deployment software, platformvirtualization (e.g., a hypervisor layer), or the like). In some cases,an IaaS provider may also supply a variety of services to accompanythose infrastructure components (e.g., billing, monitoring, logging,security, load balancing and clustering, etc.). Thus, as these servicesmay be policy-driven, IaaS users may be able to implement policies todrive load balancing to maintain application availability andperformance. CSPI provides infrastructure and a set of complementarycloud services that enable customers to build and run a wide range ofapplications and services in a highly available hosted distributedenvironment. CSPI offers high-performance compute resources andcapabilities and storage capacity in a flexible virtual network that issecurely accessible from various networked locations such as from acustomer's on-premises network. When a customer subscribes to orregisters for an IaaS service provided by a CSP, the tenancy created forthat customer is a secure and isolated partition within the CSPI wherethe customer can create, organize, and administer their cloud resources.

Customers can build their own virtual networks using compute, memory,and networking resources provided by CSPI. One or more customerresources or workloads, such as compute instances, can be deployed onthese virtual networks. For example, a customer can use resourcesprovided by CSPI to build one or multiple customizable and privatevirtual network(s) referred to as virtual cloud networks (VCNs). Acustomer can deploy one or more customer resources, such as computeinstances, on a customer VCN. Compute instances can take the form ofvirtual machines, bare metal instances, and the like. The CSPI thusprovides infrastructure and a set of complementary cloud services thatenable customers to build and run a wide range of applications andservices in a highly available virtual hosted environment. The customerdoes not manage or control the underlying physical resources provided byCSPI but has control over operating systems, storage, and deployedapplications; and possibly limited control of select networkingcomponents (e.g., firewalls).

The CSP may provide a console that enables customers and networkadministrators to configure, access, and manage resources deployed inthe cloud using CSPI resources. In certain embodiments, the consoleprovides a web-based user interface that can be used to access andmanage CSPI. In some implementations, the console is a web-basedapplication provided by the CSP.

CSPI may support single-tenancy or multi-tenancy architectures. In asingle tenancy architecture, a software (e.g., an application, adatabase) or a hardware component (e.g., a host machine or a server)serves a single customer or tenant. In a multi-tenancy architecture, asoftware or a hardware component serves multiple customers or tenants.Thus, in a multi-tenancy architecture, CSPI resources are shared betweenmultiple customers or tenants. In a multi-tenancy situation, precautionsare taken and safeguards put in place within CSPI to ensure that eachtenant's data is isolated and remains invisible to other tenants.

In a physical network, a network endpoint (“endpoint”) refers to acomputing device or system that is connected to a physical network andcommunicates back and forth with the network to which it is connected. Anetwork endpoint in the physical network may be connected to a LocalArea Network (LAN), a Wide Area Network (WAN), or other type of physicalnetwork. Examples of traditional endpoints in a physical network includemodems, hubs, bridges, switches, routers, and other networking devices,physical computers (or host machines), and the like. Each physicaldevice in the physical network has a fixed network address that can beused to communicate with the device. This fixed network address can be aLayer-2 address (e.g., a MAC address), a fixed Layer-3 address (e.g., anIP address), and the like. In a virtualized environment or in a virtualnetwork, the endpoints can include various virtual endpoints such asvirtual machines that are hosted by components of the physical network(e.g., hosted by physical host machines). These endpoints in the virtualnetwork are addressed by overlay addresses such as overlay Layer-2addresses (e.g., overlay MAC addresses) and overlay Layer-3 addresses(e.g., overlay IP addresses). Network overlays enable flexibility byallowing network managers to move around the overlay addressesassociated with network endpoints using software management (e.g., viasoftware implementing a control plane for the virtual network).Accordingly, unlike in a physical network, in a virtual network, anoverlay address (e.g., an overlay IP address) can be moved from oneendpoint to another using network management software. Since the virtualnetwork is built on top of a physical network, communications betweencomponents in the virtual network involves both the virtual network andthe underlying physical network. In order to facilitate suchcommunications, the components of CSPI are configured to learn and storemappings that map overlay addresses in the virtual network to actualphysical addresses in the substrate network, and vice versa. Thesemappings are then used to facilitate the communications. Customertraffic is encapsulated to facilitate routing in the virtual network.

Accordingly, physical addresses (e.g., physical IP addresses) areassociated with components in physical networks and overlay addresses(e.g., overlay IP addresses) are associated with entities in virtualnetworks. Both the physical IP addresses and overlay IP addresses aretypes of real IP addresses. These are separate from virtual IPaddresses, where a virtual IP address maps to multiple real IPaddresses. A virtual IP address provides a 1-to-many mapping between thevirtual IP address and multiple real IP addresses.

The cloud infrastructure or CSPI is physically hosted in one or moredata centers in one or more regions around the world. The CSPI mayinclude components in the physical or substrate network and virtualizedcomponents (e.g., virtual networks, compute instances, virtual machines,etc.) that are in an virtual network built on top of the physicalnetwork components. In certain embodiments, the CSPI is organized andhosted in realms, regions and availability domains. A region istypically a localized geographic area that contains one or more datacenters. Regions are generally independent of each other and can beseparated by vast distances, for example, across countries or evencontinents. For example, a first region may be in Australia, another onein Japan, yet another one in India, and the like. CSPI resources aredivided among regions such that each region has its own independentsubset of CSPI resources. Each region may provide a set of coreinfrastructure services and resources, such as, compute resources (e.g.,bare metal servers, virtual machine, containers and relatedinfrastructure, etc.); storage resources (e.g., block volume storage,file storage, object storage, archive storage); networking resources(e.g., virtual cloud networks (VCNs), load balancing resources,connections to on-premise networks), database resources; edge networkingresources (e.g., DNS); and access management and monitoring resources,and others. Each region generally has multiple paths connecting it toother regions in the realm.

Generally, an application is deployed in a region (i.e., deployed oninfrastructure associated with that region) where it is most heavilyused, because using nearby resources is faster than using distantresources. Applications can also be deployed in different regions forvarious reasons, such as redundancy to mitigate the risk of region-wideevents such as large weather systems or earthquakes, to meet varyingrequirements for legal jurisdictions, tax domains, and other business orsocial criteria, and the like.

The data centers within a region can be further organized and subdividedinto availability domains (ADs). An availability domain may correspondto one or more data centers located within a region. A region can becomposed of one or more availability domains. In such a distributedenvironment, CSPI resources are either region-specific, such as avirtual cloud network (VCN), or availability domain-specific, such as acompute instance.

ADs within a region are isolated from each other, fault tolerant, andare configured such that they are very unlikely to fail simultaneously.This is achieved by the ADs not sharing critical infrastructureresources such as networking, physical cables, cable paths, cable entrypoints, etc., such that a failure at one AD within a region is unlikelyto impact the availability of the other ADs within the same region. TheADs within the same region may be connected to each other by a lowlatency, high bandwidth network, which makes it possible to providehigh-availability connectivity to other networks (e.g., the Internet,customers' on-premise networks, etc.) and to build replicated systems inmultiple ADs for both high-availability and disaster recovery. Cloudservices use multiple ADs to ensure high availability and to protectagainst resource failure. As the infrastructure provided by the IaaSprovider grows, more regions and ADs may be added with additionalcapacity. Traffic between availability domains is usually encrypted.

In certain embodiments, regions are grouped into realms. A realm is alogical collection of regions. Realms are isolated from each other anddo not share any data. Regions in the same realm may communicate witheach other, but regions in different realms cannot. A customer's tenancyor account with the CSP exists in a single realm and can be spreadacross one or more regions that belong to that realm. Typically, when acustomer subscribes to an IaaS service, a tenancy or account is createdfor that customer in the customer-specified region (referred to as the“home” region) within a realm. A customer can extend the customer'stenancy across one or more other regions within the realm. A customercannot access regions that are not in the realm where the customer'stenancy exists.

An IaaS provider can provide multiple realms, each realm catered to aparticular set of customers or users. For example, a commercial realmmay be provided for commercial customers. As another example, a realmmay be provided for a specific country for customers within thatcountry. As yet another example, a government realm may be provided fora government, and the like. For example, the government realm may becatered for a specific government and may have a heightened level ofsecurity than a commercial realm. For example, Oracle CloudInfrastructure (OCI) currently offers a realm for commercial regions andtwo realms (e.g., FedRAMP authorized and IL5 authorized) for governmentcloud regions.

In certain embodiments, an AD can be subdivided into one or more faultdomains. A fault domain is a grouping of infrastructure resources withinan AD to provide anti-affinity. Fault domains allow for the distributionof compute instances such that the instances are not on the samephysical hardware within a single AD. This is known as anti-affinity. Afault domain refers to a set of hardware components (computers,switches, and more) that share a single point of failure. A compute poolis logically divided up into fault domains. Due to this, a hardwarefailure or compute hardware maintenance event that affects one faultdomain does not affect instances in other fault domains. Depending onthe embodiment, the number of fault domains for each AD may vary. Forinstance, in certain embodiments each AD contains three fault domains. Afault domain acts as a logical data center within an AD.

When a customer subscribes to an IaaS service, resources from CSPI areprovisioned for the customer and associated with the customer's tenancy.The customer can use these provisioned resources to build privatenetworks and deploy resources on these networks. The customer networksthat are hosted in the cloud by the CSPI are referred to as virtualcloud networks (VCNs). A customer can set up one or more virtual cloudnetworks (VCNs) using CSPI resources allocated for the customer. A VCNis a virtual or software defined private network. The customer resourcesthat are deployed in the customer's VCN can include compute instances(e.g., virtual machines, bare-metal instances) and other resources.These compute instances may represent various customer workloads such asapplications, load balancers, databases, and the like. A computeinstance deployed on a VCN can communicate with public accessibleendpoints (“public endpoints”) over a public network such as theInternet, with other instances in the same VCN or other VCNs (e.g., thecustomer's other VCNs, or VCNs not belonging to the customer), with thecustomer's on-premise data centers or networks, and with serviceendpoints, and other types of endpoints.

The CSP may provide various services using the CSPI. In some instances,customers of CSPI may themselves act like service providers and provideservices using CSPI resources. A service provider may expose a serviceendpoint, which is characterized by identification information (e.g., anIP Address, a DNS name and port). A customer's resource (e.g., a computeinstance) can consume a particular service by accessing a serviceendpoint exposed by the service for that particular service. Theseservice endpoints are generally endpoints that are publicly accessibleby users using public IP addresses associated with the endpoints via apublic communication network such as the Internet. Network endpointsthat are publicly accessible are also sometimes referred to as publicendpoints.

In certain embodiments, a service provider may expose a service via anendpoint (sometimes referred to as a service endpoint) for the service.Customers of the service can then use this service endpoint to accessthe service. In certain implementations, a service endpoint provided fora service can be accessed by multiple customers that intend to consumethat service. In other implementations, a dedicated service endpoint maybe provided for a customer such that only that customer can access theservice using that dedicated service endpoint.

In certain embodiments, when a VCN is created, it is associated with aprivate overlay Classless Inter-Domain Routing (CIDR) address space,which is a range of private overlay IP addresses that are assigned tothe VCN (e.g., 10.0/16). A VCN includes associated subnets, routetables, and gateways. A VCN resides within a single region but can spanone or more or all of the region's availability domains. A gateway is avirtual interface that is configured for a VCN and enables communicationof traffic to and from the VCN to one or more endpoints outside the VCN.One or more different types of gateways may be configured for a VCN toenable communication to and from different types of endpoints.

A VCN can be subdivided into one or more sub-networks such as one ormore subnets. A subnet is thus a unit of configuration or a subdivisionthat can be created within a VCN. A VCN can have one or multiplesubnets. Each subnet within a VCN is associated with a contiguous rangeof overlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do notoverlap with other subnets in that VCN and which represent an addressspace subset within the address space of the VCN.

Each compute instance is associated with a virtual network interfacecard (VNIC), that enables the compute instance to participate in asubnet of a VCN. A VNIC is a logical representation of physical NetworkInterface Card (NIC). In general. a VNIC is an interface between anentity (e.g., a compute instance, a service) and a virtual network. AVNIC exists in a subnet, has one or more associated IP addresses, andassociated security rules or policies. A VNIC is equivalent to a Layer-2port on a switch. A VNIC is attached to a compute instance and to asubnet within a VCN. A VNIC associated with a compute instance enablesthe compute instance to be a part of a subnet of a VCN and enables thecompute instance to communicate (e.g., send and receive packets) withendpoints that are on the same subnet as the compute instance, withendpoints in different subnets in the VCN, or with endpoints outside theVCN. The VNIC associated with a compute instance thus determines how thecompute instance connects with endpoints inside and outside the VCN. AVNIC for a compute instance is created and associated with that computeinstance when the compute instance is created and added to a subnetwithin a VCN. For a subnet comprising a set of compute instances, thesubnet contains the VNICs corresponding to the set of compute instances,each VNIC attached to a compute instance within the set of computerinstances.

Each compute instance is assigned a private overlay IP address via theVNIC associated with the compute instance. This private overlay IPaddress is assigned to the VNIC that is associated with the computeinstance when the compute instance is created and used for routingtraffic to and from the compute instance. All VNICs in a given subnetuse the same route table, security lists, and DHCP options. As describedabove, each subnet within a VCN is associated with a contiguous range ofoverlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do notoverlap with other subnets in that VCN and which represent an addressspace subset within the address space of the VCN. For a VNIC on aparticular subnet of a VCN, the private overlay IP address that isassigned to the VNIC is an address from the contiguous range of overlayIP addresses allocated for the subnet.

In certain embodiments, a compute instance may optionally be assignedadditional overlay IP addresses in addition to the private overlay IPaddress, such as, for example, one or more public IP addresses if in apublic subnet. These multiple addresses are assigned either on the sameVNIC or over multiple VNICs that are associated with the computeinstance. Each instance however has a primary VNIC that is createdduring instance launch and is associated with the overlay private IPaddress assigned to the instance—this primary VNIC cannot be removed.Additional VNICs, referred to as secondary VNICs, can be added to anexisting instance in the same availability domain as the primary VNIC.All the VNICs are in the same availability domain as the instance. Asecondary VNIC can be in a subnet in the same VCN as the primary VNIC,or in a different subnet that is either in the same VCN or a differentone.

A compute instance may optionally be assigned a public IP address if itis in a public subnet. A subnet can be designated as either a publicsubnet or a private subnet at the time the subnet is created. A privatesubnet means that the resources (e.g., compute instances) and associatedVNICs in the subnet cannot have public overlay IP addresses. A publicsubnet means that the resources and associated VNICs in the subnet canhave public IP addresses. A customer can designate a subnet to existeither in a single availability domain or across multiple availabilitydomains in a region or realm.

As described above, a VCN may be subdivided into one or more subnets. Incertain embodiments, a Virtual Router (VR) configured for the VCN(referred to as the VCN VR or just VR) enables communications betweenthe subnets of the VCN. For a subnet within a VCN, the VR represents alogical gateway for that subnet that enables the subnet (i.e., thecompute instances on that subnet) to communicate with endpoints on othersubnets within the VCN, and with other endpoints outside the VCN. TheVCN VR is a logical entity that is configured to route traffic betweenVNICs in the VCN and virtual gateways (“gateways”) associated with theVCN. Gateways are further described below with respect to FIG. 1 . A VCNVR is a Layer-3/IP Layer concept. In one embodiment, there is one VCN VRfor a VCN where the VCN VR has potentially an unlimited number of portsaddressed by IP addresses, with one port for each subnet of the VCN. Inthis manner, the VCN VR has a different IP address for each subnet inthe VCN that the VCN VR is attached to. The VR is also connected to thevarious gateways configured for a VCN. In certain embodiments, aparticular overlay IP address from the overlay IP address range for asubnet is reserved for a port of the VCN VR for that subnet. Forexample, consider a VCN having two subnets with associated addressranges 10.0/16 and 10.1/16, respectively. For the first subnet withinthe VCN with address range 10.0/16, an address from this range isreserved for a port of the VCN VR for that subnet. In some instances,the first IP address from the range may be reserved for the VCN VR. Forexample, for the subnet with overlay IP address range 10.0/16, IPaddress 10.0.0.1 may be reserved for a port of the VCN VR for thatsubnet. For the second subnet within the same VCN with address range10.1/16, the VCN VR may have a port for that second subnet with IPaddress 10.1.0.1. The VCN VR has a different IP address for each of thesubnets in the VCN.

In some other embodiments, each subnet within a VCN may have its ownassociated VR that is addressable by the subnet using a reserved ordefault IP address associated with the VR. The reserved or default IPaddress may, for example, be the first IP address from the range of IPaddresses associated with that subnet. The VNICs in the subnet cancommunicate (e.g., send and receive packets) with the VR associated withthe subnet using this default or reserved IP address. In such anembodiment, the VR is the ingress/egress point for that subnet. The VRassociated with a subnet within the VCN can communicate with other VRsassociated with other subnets within the VCN. The VRs can alsocommunicate with gateways associated with the VCN. The VR function for asubnet is running on or executed by one or more NVDs executing VNICsfunctionality for VNICs in the subnet.

Route tables, security rules, and DHCP options may be configured for aVCN. Route tables are virtual route tables for the VCN and include rulesto route traffic from subnets within the VCN to destinations outside theVCN by way of gateways or specially configured instances. A VCN's routetables can be customized to control how packets are forwarded/routed toand from the VCN. DHCP options refers to configuration information thatis automatically provided to the instances when they boot up.

Security rules configured for a VCN represent overlay firewall rules forthe VCN. The security rules can include ingress and egress rules, andspecify the types of traffic (e.g., based upon protocol and port) thatis allowed in and out of the instances within the VCN. The customer canchoose whether a given rule is stateful or stateless. For instance, thecustomer can allow incoming SSH traffic from anywhere to a set ofinstances by setting up a stateful ingress rule with source CIDR0.0.0.0/0, and destination TCP port 22. Security rules can beimplemented using network security groups or security lists. A networksecurity group consists of a set of security rules that apply only tothe resources in that group. A security list, on the other hand,includes rules that apply to all the resources in any subnet that usesthe security list. A VCN may be provided with a default security listwith default security rules. DHCP options configured for a VCN provideconfiguration information that is automatically provided to theinstances in the VCN when the instances boot up.

In certain embodiments, the configuration information for a VCN isdetermined and stored by a VCN Control Plane. The configurationinformation for a VCN may include, for example, information about: theaddress range associated with the VCN, subnets within the VCN andassociated information, one or more VRs associated with the VCN, computeinstances in the VCN and associated VNICs, NVDs executing the variousvirtualization network functions (e.g., VNICs, VRs, gateways) associatedwith the VCN, state information for the VCN, and other VCN-relatedinformation. In certain embodiments, a VCN Distribution Servicepublishes the configuration information stored by the VCN Control Plane,or portions thereof, to the NVDs. The distributed information may beused to update information (e.g., forwarding tables, routing tables,etc.) stored and used by the NVDs to forward packets to and from thecompute instances in the VCN.

In certain embodiments, the creation of VCNs and subnets are handled bya VCN Control Plane (CP) and the launching of compute instances ishandled by a Compute Control Plane. The Compute Control Plane isresponsible for allocating the physical resources for the computeinstance and then calls the VCN Control Plane to create and attach VNICsto the compute instance. The VCN CP also sends VCN data mappings to theVCN data plane that is configured to perform packet forwarding androuting functions. In certain embodiments, the VCN CP provides adistribution service that is responsible for providing updates to theVCN data plane. Examples of a VCN Control Plane are also depicted inFIGS. 17, 18, 19, and 20 (see references 1716, 1816, 1916, and 2016) anddescribed below.

A customer may create one or more VCNs using resources hosted by CSPI. Acompute instance deployed on a customer VCN may communicate withdifferent endpoints. These endpoints can include endpoints that arehosted by CSPI and endpoints outside CSPI.

Various different architectures for implementing cloud-based serviceusing CSPI are depicted in FIGS. 1, 2, 3, 4, 5, 17, 18, 19, and 21 , andare described below. FIG. 1 is a high level diagram of a distributedenvironment 100 showing an overlay or customer VCN hosted by CSPIaccording to certain embodiments. The distributed environment depictedin FIG. 1 includes multiple components in the overlay network.Distributed environment 100 depicted in FIG. 1 is merely an example andis not intended to unduly limit the scope of claimed embodiments. Manyvariations, alternatives, and modifications are possible. For example,in some implementations, the distributed environment depicted in FIG. 1may have more or fewer systems or components than those shown in FIG. 1, may combine two or more systems, or may have a different configurationor arrangement of systems.

As shown in the example depicted in FIG. 1 , distributed environment 100comprises CSPI 101 that provides services and resources that customerscan subscribe to and use to build their virtual cloud networks (VCNs).In certain embodiments, CSPI 101 offers IaaS services to subscribingcustomers. The data centers within CSPI 101 may be organized into one ormore regions. One example region “Region US” 102 is shown in FIG. 1 . Acustomer has configured a customer VCN 104 for region 102. The customermay deploy various compute instances on VCN 104, where the computeinstances may include virtual machines or bare metal instances. Examplesof instances include applications, database, load balancers, and thelike.

In the embodiment depicted in FIG. 1 , customer VCN 104 comprises twosubnets, namely, “Subnet-1” and “Subnet-2”, each subnet with its ownCIDR IP address range. In FIG. 1 , the overlay IP address range forSubnet-1 is 10.0/16 and the address range for Subnet-2 is 10.1/16. A VCNVirtual Router 105 represents a logical gateway for the VCN that enablescommunications between subnets of the VCN 104, and with other endpointsoutside the VCN. VCN VR 105 is configured to route traffic between VNICsin VCN 104 and gateways associated with VCN 104. VCN VR 105 provides aport for each subnet of VCN 104. For example, VR 105 may provide a portwith IP address 10.0.0.1 for Subnet-1 and a port with IP address10.1.0.1 for Subnet-2.

Multiple compute instances may be deployed on each subnet, where thecompute instances can be virtual machine instances, and/or bare metalinstances. The compute instances in a subnet may be hosted by one ormore host machines within CSPI 101. A compute instance participates in asubnet via a VNIC associated with the compute instance. For example, asshown in FIG. 1 , a compute instance C1 is part of Subnet-1 via a VNICassociated with the compute instance. Likewise, compute instance C2 ispart of Subnet-1 via a VNIC associated with C2. In a similar manner,multiple compute instances, which may be virtual machine instances orbare metal instances, may be part of Subnet-1. Via its associated VNIC,each compute instance is assigned a private overlay IP address and a MACaddress. For example, in FIG. 1 , compute instance C1 has an overlay IPaddress of 10.0.0.2 and a MAC address of M1, while compute instance C2has an private overlay IP address of 10.0.0.3 and a MAC address of M2.Each compute instance in Subnet-1, including compute instances C1 andC2, has a default route to VCN VR 105 using IP address 10.0.0.1, whichis the IP address for a port of VCN VR 105 for Subnet-1.

Subnet-2 can have multiple compute instances deployed on it, includingvirtual machine instances and/or bare metal instances. For example, asshown in FIG. 1 , compute instances D1 and D2 are part of Subnet-2 viaVNICs associated with the respective compute instances. In theembodiment depicted in FIG. 1 , compute instance D1 has an overlay IPaddress of 10.1.0.2 and a MAC address of MM1, while compute instance D2has an private overlay IP address of 10.1.0.3 and a MAC address of MM2.Each compute instance in Subnet-2, including compute instances D1 andD2, has a default route to VCN VR 105 using IP address 10.1.0.1, whichis the IP address for a port of VCN VR 105 for Subnet-2.

VCN A 104 may also include one or more load balancers. For example, aload balancer may be provided for a subnet and may be configured to loadbalance traffic across multiple compute instances on the subnet. A loadbalancer may also be provided to load balance traffic across subnets inthe VCN.

A particular compute instance deployed on VCN 104 can communicate withvarious different endpoints. These endpoints may include endpoints thatare hosted by CSPI 200 and endpoints outside CSPI 200. Endpoints thatare hosted by CSPI 101 may include: an endpoint on the same subnet asthe particular compute instance (e.g., communications between twocompute instances in Subnet-1); an endpoint on a different subnet butwithin the same VCN (e.g., communication between a compute instance inSubnet-1 and a compute instance in Subnet-2); an endpoint in a differentVCN in the same region (e.g., communications between a compute instancein Subnet-1 and an endpoint in a VCN in the same region 106 or 110,communications between a compute instance in Subnet-1 and an endpoint inservice network 110 in the same region); or an endpoint in a VCN in adifferent region (e.g., communications between a compute instance inSubnet-1 and an endpoint in a VCN in a different region 108). A computeinstance in a subnet hosted by CSPI 101 may also communicate withendpoints that are not hosted by CSPI 101 (i.e., are outside CSPI 101).These outside endpoints include endpoints in the customer's on-premisenetwork 116, endpoints within other remote cloud hosted networks 118,public endpoints 114 accessible via a public network such as theInternet, and other endpoints.

Communications between compute instances on the same subnet arefacilitated using VNICs associated with the source compute instance andthe destination compute instance. For example, compute instance C1 inSubnet-1 may want to send packets to compute instance C2 in Subnet-1.For a packet originating at a source compute instance and whosedestination is another compute instance in the same subnet, the packetis first processed by the VNIC associated with the source computeinstance. Processing performed by the VNIC associated with the sourcecompute instance can include determining destination information for thepacket from the packet headers, identifying any policies (e.g., securitylists) configured for the VNIC associated with the source computeinstance, determining a next hop for the packet, performing any packetencapsulation/decapsulation functions as needed, and thenforwarding/routing the packet to the next hop with the goal offacilitating communication of the packet to its intended destination.When the destination compute instance is in the same subnet as thesource compute instance, the VNIC associated with the source computeinstance is configured to identify the VNIC associated with thedestination compute instance and forward the packet to that VNIC forprocessing. The VNIC associated with the destination compute instance isthen executed and forwards the packet to the destination computeinstance.

For a packet to be communicated from a compute instance in a subnet toan endpoint in a different subnet in the same VCN, the communication isfacilitated by the VNICs associated with the source and destinationcompute instances and the VCN VR. For example, if compute instance C1 inSubnet-1 in FIG. 1 wants to send a packet to compute instance D1 inSubnet-2, the packet is first processed by the VNIC associated withcompute instance C1. The VNIC associated with compute instance C1 isconfigured to route the packet to the VCN VR 105 using default route orport 10.0.0.1 of the VCN VR. VCN VR 105 is configured to route thepacket to Subnet-2 using port 10.1.0.1. The packet is then received andprocessed by the VNIC associated with D1 and the VNIC forwards thepacket to compute instance D1.

For a packet to be communicated from a compute instance in VCN 104 to anendpoint that is outside VCN 104, the communication is facilitated bythe VNIC associated with the source compute instance, VCN VR 105, andgateways associated with VCN 104. One or more types of gateways may beassociated with VCN 104. A gateway is an interface between a VCN andanother endpoint, where the another endpoint is outside the VCN. Agateway is a Layer-3/IP layer concept and enables a VCN to communicatewith endpoints outside the VCN. A gateway thus facilitates traffic flowbetween a VCN and other VCNs or networks. Various different types ofgateways may be configured for a VCN to facilitate different types ofcommunications with different types of endpoints. Depending upon thegateway, the communications may be over public networks (e.g., theInternet) or over private networks. Various communication protocols maybe used for these communications.

For example, compute instance C1 may want to communicate with anendpoint outside VCN 104. The packet may be first processed by the VNICassociated with source compute instance C1. The VNIC processingdetermines that the destination for the packet is outside the Subnet-1of C1. The VNIC associated with C1 may forward the packet to VCN VR 105for VCN 104. VCN VR 105 then processes the packet and as part of theprocessing, based upon the destination for the packet, determines aparticular gateway associated with VCN 104 as the next hop for thepacket. VCN VR 105 may then forward the packet to the particularidentified gateway. For example, if the destination is an endpointwithin the customer's on-premise network, then the packet may beforwarded by VCN VR 105 to Dynamic Routing Gateway (DRG) gateway 122configured for VCN 104. The packet may then be forwarded from thegateway to a next hop to facilitate communication of the packet to itfinal intended destination.

Various different types of gateways may be configured for a VCN.Examples of gateways that may be configured for a VCN are depicted inFIG. 1 and described below. Examples of gateways associated with a VCNare also depicted in FIGS. 17, 18, 19, and 20 (for example, gatewaysreferenced by reference numbers 1734, 1736, 1738, 1834, 1836, 1838,1934, 1936, 1938, 2034, 2036, and 2038) and described below. As shown inthe embodiment depicted in FIG. 1 , a Dynamic Routing Gateway (DRG) 122may be added to or be associated with customer VCN 104 and provides apath for private network traffic communication between customer VCN 104and another endpoint, where the another endpoint can be the customer'son-premise network 116, a VCN 108 in a different region of CSPI 101, orother remote cloud networks 118 not hosted by CSPI 101. Customeron-premise network 116 may be a customer network or a customer datacenter built using the customer's resources. Access to customeron-premise network 116 is generally very restricted. For a customer thathas both a customer on-premise network 116 and one or more VCNs 104deployed or hosted in the cloud by CSPI 101, the customer may want theiron-premise network 116 and their cloud-based VCN 104 to be able tocommunicate with each other. This enables a customer to build anextended hybrid environment encompassing the customer's VCN 104 hostedby CSPI 101 and their on-premises network 116. DRG 122 enables thiscommunication. To enable such communications, a communication channel124 is set up where one endpoint of the channel is in customeron-premise network 116 and the other endpoint is in CSPI 101 andconnected to customer VCN 104. Communication channel 124 can be overpublic communication networks such as the Internet or privatecommunication networks. Various different communication protocols may beused such as IPsec VPN technology over a public communication networksuch as the Internet, Oracle's FastConnect technology that uses aprivate network instead of a public network, and others. The device orequipment in customer on-premise network 116 that forms one end pointfor communication channel 124 is referred to as the customer premiseequipment (CPE), such as CPE 126 depicted in FIG. 1 . On the CSPI 101side, the endpoint may be a host machine executing DRG 122.

In certain embodiments, a Remote Peering Connection (RPC) can be addedto a DRG, which allows a customer to peer one VCN with another VCN in adifferent region. Using such an RPC, customer VCN 104 can use DRG 122 toconnect with a VCN 108 in another region. DRG 122 may also be used tocommunicate with other remote cloud networks 118, not hosted by CSPI 101such as a Microsoft Azure cloud, Amazon AWS cloud, and others.

As shown in FIG. 1 , an Internet Gateway (IGW) 120 may be configured forcustomer VCN 104 the enables a compute instance on VCN 104 tocommunicate with public endpoints 114 accessible over a public networksuch as the Internet. IGW 1120 is a gateway that connects a VCN to apublic network such as the Internet. IGW 120 enables a public subnet(where the resources in the public subnet have public overlay IPaddresses) within a VCN, such as VCN 104, direct access to publicendpoints 112 on a public network 114 such as the Internet. Using IGW120, connections can be initiated from a subnet within VCN 104 or fromthe Internet.

A Network Address Translation (NAT) gateway 128 can be configured forcustomer's VCN 104 and enables cloud resources in the customer's VCN,which do not have dedicated public overlay IP addresses, access to theInternet and it does so without exposing those resources to directincoming Internet connections (e.g., L4-L7 connections). This enables aprivate subnet within a VCN, such as private Subnet-1 in VCN 104, withprivate access to public endpoints on the Internet. In NAT gateways,connections can be initiated only from the private subnet to the publicInternet and not from the Internet to the private subnet.

In certain embodiments, a Service Gateway (SGW) 126 can be configuredfor customer VCN 104 and provides a path for private network trafficbetween VCN 104 and supported services endpoints in a service network110. In certain embodiments, service network 110 may be provided by theCSP and may provide various services. An example of such a servicenetwork is Oracle's Services Network, which provides various servicesthat can be used by customers. For example, a compute instance (e.g., adatabase system) in a private subnet of customer VCN 104 can back updata to a service endpoint (e.g., Object Storage) without needing publicIP addresses or access to the Internet. In certain embodiments, a VCNcan have only one SGW, and connections can only be initiated from asubnet within the VCN and not from service network 110. If a VCN ispeered with another, resources in the other VCN typically cannot accessthe SGW. Resources in on-premises networks that are connected to a VCNwith FastConnect or VPN Connect can also use the service gatewayconfigured for that VCN.

In certain implementations, SGW 126 uses the concept of a serviceClassless Inter-Domain Routing (CIDR) label, which is a string thatrepresents all the regional public IP address ranges for the service orgroup of services of interest. The customer uses the service CIDR labelwhen they configure the SGW and related route rules to control trafficto the service. The customer can optionally utilize it when configuringsecurity rules without needing to adjust them if the service's public IPaddresses change in the future.

A Local Peering Gateway (LPG) 132 is a gateway that can be added tocustomer VCN 104 and enables VCN 104 to peer with another VCN in thesame region. Peering means that the VCNs communicate using private IPaddresses, without the traffic traversing a public network such as theInternet or without routing the traffic through the customer'son-premises network 116. In preferred embodiments, a VCN has a separateLPG for each peering it establishes. Local Peering or VCN Peering is acommon practice used to establish network connectivity between differentapplications or infrastructure management functions.

Service providers, such as providers of services in service network 110,may provide access to services using different access models. Accordingto a public access model, services may be exposed as public endpointsthat are publicly accessible by compute instance in a customer VCN via apublic network such as the Internet and or may be privately accessiblevia SGW 126. According to a specific private access model, services aremade accessible as private IP endpoints in a private subnet in thecustomer's VCN. This is referred to as a Private Endpoint (PE) accessand enables a service provider to expose their service as an instance inthe customer's private network. A Private Endpoint resource represents aservice within the customer's VCN. Each PE manifests as a VNIC (referredto as a PE-VNIC, with one or more private IPs) in a subnet chosen by thecustomer in the customer's VCN. A PE thus provides a way to present aservice within a private customer VCN subnet using a VNIC. Since theendpoint is exposed as a VNIC, all the features associates with a VNICsuch as routing rules, security lists, etc., are now available for thePE VNIC.

A service provider can register their service to enable access through aPE. The provider can associate policies with the service that restrictsthe service's visibility to the customer tenancies. A provider canregister multiple services under a single virtual IP address (VIP),especially for multi-tenant services. There may be multiple such privateendpoints (in multiple VCNs) that represent the same service.

Compute instances in the private subnet can then use the PE VNIC'sprivate IP address or the service DNS name to access the service.Compute instances in the customer VCN can access the service by sendingtraffic to the private IP address of the PE in the customer VCN. APrivate Access Gateway (PAGW) 130 is a gateway resource that can beattached to a service provider VCN (e.g., a VCN in service network 110)that acts as an ingress/egress point for all traffic from/to customersubnet private endpoints. PAGW 130 enables a provider to scale thenumber of PE connections without utilizing its internal IP addressresources. A provider needs only configure one PAGW for any number ofservices registered in a single VCN. Providers can represent a serviceas a private endpoint in multiple VCNs of one or more customers. Fromthe customer's perspective, the PE VNIC, which, instead of beingattached to a customer's instance, appears attached to the service withwhich the customer wishes to interact. The traffic destined to theprivate endpoint is routed via PAGW 130 to the service. These arereferred to as customer-to-service private connections (C2Sconnections).

The PE concept can also be used to extend the private access for theservice to customer's on-premises networks and data centers, by allowingthe traffic to flow through FastConnect/IPsec links and the privateendpoint in the customer VCN. Private access for the service can also beextended to the customer's peered VCNs, by allowing the traffic to flowbetween LPG 132 and the PE in the customer's VCN.

A customer can control routing in a VCN at the subnet level, so thecustomer can specify which subnets in the customer's VCN, such as VCN104, use each gateway. A VCN's route tables are used to decide iftraffic is allowed out of a VCN through a particular gateway. Forexample, in a particular instance, a route table for a public subnetwithin customer VCN 104 may send non-local traffic through IGW 120. Theroute table for a private subnet within the same customer VCN 104 maysend traffic destined for CSP services through SGW 126. All remainingtraffic may be sent via the NAT gateway 128. Route tables only controltraffic going out of a VCN.

Security lists associated with a VCN are used to control traffic thatcomes into a VCN via a gateway via inbound connections. All resources ina subnet use the same route table and security lists. Security lists maybe used to control specific types of traffic allowed in and out ofinstances in a subnet of a VCN. Security list rules may comprise ingress(inbound) and egress (outbound) rules. For example, an ingress rule mayspecify an allowed source address range, while an egress rule mayspecify an allowed destination address range. Security rules may specifya particular protocol (e.g., TCP, ICMP), a particular port (e.g., 22 forSSH, 3389 for Windows RDP), etc. In certain implementations, aninstance's operating system may enforce its own firewall rules that arealigned with the security list rules. Rules may be stateful (e.g., aconnection is tracked and the response is automatically allowed withoutan explicit security list rule for the response traffic) or stateless.

Access from a customer VCN (i.e., by a resource or compute instancedeployed on VCN 104) can be categorized as public access, privateaccess, or dedicated access. Public access refers to an access modelwhere a public IP address or a NAT is used to access a public endpoint.Private access enables customer workloads in VCN 104 with private IPaddresses (e.g., resources in a private subnet) to access serviceswithout traversing a public network such as the Internet. In certainembodiments, CSPI 101 enables customer VCN workloads with private IPaddresses to access the (public service endpoints of) services using aservice gateway. A service gateway thus offers a private access model byestablishing a virtual link between the customer's VCN and the service'spublic endpoint residing outside the customer's private network.

Additionally, CSPI may offer dedicated public access using technologiessuch as FastConnect public peering where customer on-premises instancescan access one or more services in a customer VCN using a FastConnectconnection and without traversing a public network such as the Internet.CSPI also may also offer dedicated private access using FastConnectprivate peering where customer on-premises instances with private IPaddresses can access the customer's VCN workloads using a FastConnectconnection. FastConnect is a network connectivity alternative to usingthe public Internet to connect a customer's on-premise network to CSPIand its services. FastConnect provides an easy, elastic, and economicalway to create a dedicated and private connection with higher bandwidthoptions and a more reliable and consistent networking experience whencompared to Internet-based connections.

FIG. 1 and the accompanying description above describes variousvirtualized components in an example virtual network. As describedabove, the virtual network is built on the underlying physical orsubstrate network. FIG. 2 depicts a simplified architectural diagram ofthe physical components in the physical network within CSPI 200 thatprovide the underlay for the virtual network according to certainembodiments. As shown, CSPI 200 provides a distributed environmentcomprising components and resources (e.g., compute, memory, andnetworking resources) provided by a cloud service provider (CSP). Thesecomponents and resources are used to provide cloud services (e.g., IaaSservices) to subscribing customers, i.e., customers that have subscribedto one or more services provided by the CSP. Based upon the servicessubscribed to by a customer, a subset of resources (e.g., compute,memory, and networking resources) of CSPI 200 are provisioned for thecustomer. Customers can then build their own cloud-based (i.e.,CSPI-hosted) customizable and private virtual networks using physicalcompute, memory, and networking resources provided by CSPI 200. Aspreviously indicated, these customer networks are referred to as virtualcloud networks (VCNs). A customer can deploy one or more customerresources, such as compute instances, on these customer VCNs. Computeinstances can be in the form of virtual machines, bare metal instances,and the like. CSPI 200 provides infrastructure and a set ofcomplementary cloud services that enable customers to build and run awide range of applications and services in a highly available hostedenvironment.

In the example embodiment depicted in FIG. 2 , the physical componentsof CSPI 200 include one or more physical host machines or physicalservers (e.g., 202, 206, 208), network virtualization devices (NVDs)(e.g., 210, 212), top-of-rack (TOR) switches (e.g., 214, 216), and aphysical network (e.g., 218), and switches in physical network 218. Thephysical host machines or servers may host and execute various computeinstances that participate in one or more subnets of a VCN. The computeinstances may include virtual machine instances, and bare metalinstances. For example, the various compute instances depicted in FIG. 1may be hosted by the physical host machines depicted in FIG. 2 . Thevirtual machine compute instances in a VCN may be executed by one hostmachine or by multiple different host machines. The physical hostmachines may also host virtual host machines, container-based hosts orfunctions, and the like. The VNICs and VCN VR depicted in FIG. 1 may beexecuted by the NVDs depicted in FIG. 2 . The gateways depicted in FIG.1 may be executed by the host machines and/or by the NVDs depicted inFIG. 2 .

The host machines or servers may execute a hypervisor (also referred toas a virtual machine monitor or VMM) that creates and enables avirtualized environment on the host machines. The virtualization orvirtualized environment facilitates cloud-based computing. One or morecompute instances may be created, executed, and managed on a hostmachine by a hypervisor on that host machine. The hypervisor on a hostmachine enables the physical computing resources of the host machine(e.g., compute, memory, and networking resources) to be shared betweenthe various compute instances executed by the host machine.

For example, as depicted in FIG. 2 , host machines 202 and 208 executehypervisors 260 and 266, respectively. These hypervisors may beimplemented using software, firmware, or hardware, or combinationsthereof. Typically, a hypervisor is a process or a software layer thatsits on top of the host machine's operating system (OS), which in turnexecutes on the hardware processors of the host machine. The hypervisorprovides a virtualized environment by enabling the physical computingresources (e.g., processing resources such as processors/cores, memoryresources, networking resources) of the host machine to be shared amongthe various virtual machine compute instances executed by the hostmachine. For example, in FIG. 2 , hypervisor 260 may sit on top of theOS of host machine 202 and enables the computing resources (e.g.,processing, memory, and networking resources) of host machine 202 to beshared between compute instances (e.g., virtual machines) executed byhost machine 202. A virtual machine can have its own operating system(referred to as a guest operating system), which may be the same as ordifferent from the OS of the host machine. The operating system of avirtual machine executed by a host machine may be the same as ordifferent from the operating system of another virtual machine executedby the same host machine. A hypervisor thus enables multiple operatingsystems to be executed alongside each other while sharing the samecomputing resources of the host machine. The host machines depicted inFIG. 2 may have the same or different types of hypervisors.

A compute instance can be a virtual machine instance or a bare metalinstance. In FIG. 2 , compute instances 268 on host machine 202 and 274on host machine 208 are examples of virtual machine instances. Hostmachine 206 is an example of a bare metal instance that is provided to acustomer.

In certain instances, an entire host machine may be provisioned to asingle customer, and all of the one or more compute instances (eithervirtual machines or bare metal instance) hosted by that host machinebelong to that same customer. In other instances, a host machine may beshared between multiple customers (i.e., multiple tenants). In such amulti-tenancy scenario, a host machine may host virtual machine computeinstances belonging to different customers. These compute instances maybe members of different VCNs of different customers. In certainembodiments, a bare metal compute instance is hosted by a bare metalserver without a hypervisor. When a bare metal compute instance isprovisioned, a single customer or tenant maintains control of thephysical CPU, memory, and network interfaces of the host machine hostingthe bare metal instance and the host machine is not shared with othercustomers or tenants.

As previously described, each compute instance that is part of a VCN isassociated with a VNIC that enables the compute instance to become amember of a subnet of the VCN. The VNIC associated with a computeinstance facilitates the communication of packets or frames to and fromthe compute instance. A VNIC is associated with a compute instance whenthe compute instance is created. In certain embodiments, for a computeinstance executed by a host machine, the VNIC associated with thatcompute instance is executed by an NVD connected to the host machine.For example, in FIG. 2 , host machine 202 executes a virtual machinecompute instance 268 that is associated with VNIC 276, and VNIC 276 isexecuted by NVD 210 connected to host machine 202. As another example,bare metal instance 272 hosted by host machine 206 is associated withVNIC 280 that is executed by NVD 212 connected to host machine 206. Asyet another example, VNIC 284 is associated with compute instance 274executed by host machine 208, and VNIC 284 is executed by NVD 212connected to host machine 208.

For compute instances hosted by a host machine, an NVD connected to thathost machine also executes VCN VRs corresponding to VCNs of which thecompute instances are members. For example, in the embodiment depictedin FIG. 2 , NVD 210 executes VCN VR 277 corresponding to the VCN ofwhich compute instance 268 is a member. NVD 212 may also execute one ormore VCN VRs 283 corresponding to VCNs corresponding to the computeinstances hosted by host machines 206 and 208.

A host machine may include one or more network interface cards (NIC)that enable the host machine to be connected to other devices. A NIC ona host machine may provide one or more ports (or interfaces) that enablethe host machine to be communicatively connected to another device. Forexample, a host machine may be connected to an NVD using one or moreports (or interfaces) provided on the host machine and on the NVD. Ahost machine may also be connected to other devices such as another hostmachine.

For example, in FIG. 2 , host machine 202 is connected to NVD 210 usinglink 220 that extends between a port 234 provided by a NIC 232 of hostmachine 202 and between a port 236 of NVD 210. Host machine 206 isconnected to NVD 212 using link 224 that extends between a port 246provided by a NIC 244 of host machine 206 and between a port 248 of NVD212. Host machine 208 is connected to NVD 212 using link 226 thatextends between a port 252 provided by a NIC 250 of host machine 208 andbetween a port 254 of NVD 212.

The NVDs are in turn connected via communication links totop-of-the-rack (TOR) switches, which are connected to physical network218 (also referred to as the switch fabric). In certain embodiments, thelinks between a host machine and an NVD, and between an NVD and a TORswitch are Ethernet links. For example, in FIG. 2 , NVDs 210 and 212 areconnected to TOR switches 214 and 216, respectively, using links 228 and230. In certain embodiments, the links 220, 224, 226, 228, and 230 areEthernet links. The collection of host machines and NVDs that areconnected to a TOR is sometimes referred to as a rack.

Physical network 218 provides a communication fabric that enables TORswitches to communicate with each other. Physical network 218 can be amulti-tiered network. In certain implementations, physical network 218is a multi-tiered Clos network of switches, with TOR switches 214 and216 representing the leaf level nodes of the multi-tiered and multi-nodephysical switching network 218. Different Clos network configurationsare possible including but not limited to a 2-tier network, a 3-tiernetwork, a 4-tier network, a 5-tier network, and in general a “n”-tierednetwork. An example of a Clos network is depicted in FIG. 5 anddescribed below.

Various different connection configurations are possible between hostmachines and NVDs such as one-to-one configuration, many-to-oneconfiguration, one-to-many configuration, and others. In a one-to-oneconfiguration implementation, each host machine is connected to its ownseparate NVD. For example, in FIG. 2 , host machine 202 is connected toNVD 210 via NIC 232 of host machine 202. In a many-to-one configuration,multiple host machines are connected to one NVD. For example, in FIG. 2, host machines 206 and 208 are connected to the same NVD 212 via NICs244 and 250, respectively.

In a one-to-many configuration, one host machine is connected tomultiple NVDs. FIG. 3 shows an example within CSPI 300 where a hostmachine is connected to multiple NVDs. As shown in FIG. 3 , host machine302 comprises a network interface card (NIC) 304 that includes multipleports 306 and 308. Host machine 300 is connected to a first NVD 310 viaport 306 and link 320, and connected to a second NVD 312 via port 308and link 322. Ports 306 and 308 may be Ethernet ports and the links 320and 322 between host machine 302 and NVDs 310 and 312 may be Ethernetlinks. NVD 310 is in turn connected to a first TOR switch 314 and NVD312 is connected to a second TOR switch 316. The links between NVDs 310and 312, and TOR switches 314 and 316 may be Ethernet links. TORswitches 314 and 316 represent the Tier-0 switching devices inmulti-tiered physical network 318.

The arrangement depicted in FIG. 3 provides two separate physicalnetwork paths to and from physical switch network 318 to host machine302: a first path traversing TOR switch 314 to NVD 310 to host machine302, and a second path traversing TOR switch 316 to NVD 312 to hostmachine 302. The separate paths provide for enhanced availability(referred to as high availability) of host machine 302. If there areproblems in one of the paths (e.g., a link in one of the paths goesdown) or devices (e.g., a particular NVD is not functioning), then theother path may be used for communications to/from host machine 302.

In the configuration depicted in FIG. 3 , the host machine is connectedto two different NVDs using two different ports provided by a NIC of thehost machine. In other embodiments, a host machine may include multipleNICs that enable connectivity of the host machine to multiple NVDs.

Referring back to FIG. 2 , an NVD is a physical device or component thatperforms one or more network and/or storage virtualization functions. AnNVD may be any device with one or more processing units (e.g., CPUs,Network Processing Units (NPUs), FPGAs, packet processing pipelines,etc.), memory including cache, and ports. The various virtualizationfunctions may be performed by software/firmware executed by the one ormore processing units of the NVD.

An NVD may be implemented in various different forms. For example, incertain embodiments, an NVD is implemented as an interface card referredto as a smartNIC or an intelligent NIC with an embedded processoronboard. A smartNIC is a separate device from the NICs on the hostmachines. In FIG. 2 , the NVDs 210 and 212 may be implemented assmartNICs that are connected to host machines 202, and host machines 206and 208, respectively.

A smartNIC is however just one example of an NVD implementation. Variousother implementations are possible. For example, in some otherimplementations, an NVD or one or more functions performed by the NVDmay be incorporated into or performed by one or more host machines, oneor more TOR switches, and other components of CSPI 200. For example, anNVD may be embodied in a host machine where the functions performed byan NVD are performed by the host machine. As another example, an NVD maybe part of a TOR switch or a TOR switch may be configured to performfunctions performed by an NVD that enables the TOR switch to performvarious complex packet transformations that are used for a public cloud.A TOR that performs the functions of an NVD is sometimes referred to asa smart TOR. In yet other implementations, where virtual machines (VMs)instances, but not bare metal (BM) instances, are offered to customers,functions performed by an NVD may be implemented inside a hypervisor ofthe host machine. In some other implementations, some of the functionsof the NVD may be offloaded to a centralized service running on a fleetof host machines.

In certain embodiments, such as when implemented as a smartNIC as shownin FIG. 2 , an NVD may comprise multiple physical ports that enable itto be connected to one or more host machines and to one or more TORswitches. A port on an NVD can be classified as a host-facing port (alsoreferred to as a “south port”) or a network-facing or TOR-facing port(also referred to as a “north port”). A host-facing port of an NVD is aport that is used to connect the NVD to a host machine. Examples ofhost-facing ports in FIG. 2 include port 236 on NVD 210, and ports 248and 254 on NVD 212. A network-facing port of an NVD is a port that isused to connect the NVD to a TOR switch. Examples of network-facingports in FIG. 2 include port 256 on NVD 210, and port 258 on NVD 212. Asshown in FIG. 2 , NVD 210 is connected to TOR switch 214 using link 228that extends from port 256 of NVD 210 to the TOR switch 214. Likewise,NVD 212 is connected to TOR switch 216 using link 230 that extends fromport 258 of NVD 212 to the TOR switch 216.

An NVD receives packets and frames from a host machine (e.g., packetsand frames generated by a compute instance hosted by the host machine)via a host-facing port and, after performing the necessary packetprocessing, may forward the packets and frames to a TOR switch via anetwork-facing port of the NVD. An NVD may receive packets and framesfrom a TOR switch via a network-facing port of the NVD and, afterperforming the necessary packet processing, may forward the packets andframes to a host machine via a host-facing port of the NVD.

In certain embodiments, there may be multiple ports and associated linksbetween an NVD and a TOR switch. These ports and links may be aggregatedto form a link aggregator group of multiple ports or links (referred toas a LAG). Link aggregation allows multiple physical links between twoend-points (e.g., between an NVD and a TOR switch) to be treated as asingle logical link. All the physical links in a given LAG may operatein full-duplex mode at the same speed. LAGs help increase the bandwidthand reliability of the connection between two endpoints. If one of thephysical links in the LAG goes down, traffic is dynamically andtransparently reassigned to one of the other physical links in the LAG.The aggregated physical links deliver higher bandwidth than eachindividual link. The multiple ports associated with a LAG are treated asa single logical port. Traffic can be load-balanced across the multiplephysical links of a LAG. One or more LAGs may be configured between twoendpoints. The two endpoints may be between an NVD and a TOR switch,between a host machine and an NVD, and the like.

An NVD implements or performs network virtualization functions. Thesefunctions are performed by software/firmware executed by the NVD.Examples of network virtualization functions include without limitation:packet encapsulation and de-capsulation functions; functions forcreating a VCN network; functions for implementing network policies suchas VCN security list (firewall) functionality; functions that facilitatethe routing and forwarding of packets to and from compute instances in aVCN; and the like. In certain embodiments, upon receiving a packet, anNVD is configured to execute a packet processing pipeline for processingthe packet and determining how the packet is to be forwarded or routed.As part of this packet processing pipeline, the NVD may execute one ormore virtual functions associated with the overlay network such asexecuting VNICs associated with cis in the VCN, executing a VirtualRouter (VR) associated with the VCN, the encapsulation and decapsulationof packets to facilitate forwarding or routing in the virtual network,execution of certain gateways (e.g., the Local Peering Gateway), theimplementation of Security Lists, Network Security Groups, networkaddress translation (NAT) functionality (e.g., the translation of PublicIP to Private IP on a host by host basis), throttling functions, andother functions.

In certain embodiments, the packet processing data path in an NVD maycomprise multiple packet pipelines, each composed of a series of packettransformation stages. In certain implementations, upon receiving apacket, the packet is parsed and classified to a single pipeline. Thepacket is then processed in a linear fashion, one stage after another,until the packet is either dropped or sent out over an interface of theNVD. These stages provide basic functional packet processing buildingblocks (e.g., validating headers, enforcing throttle, inserting newLayer-2 headers, enforcing L4 firewall, VCN encapsulation/decapsulation,etc.) so that new pipelines can be constructed by composing existingstages, and new functionality can be added by creating new stages andinserting them into existing pipelines.

An NVD may perform both control plane and data plane functionscorresponding to a control plane and a data plane of a VCN. Examples ofa VCN Control Plane are also depicted in FIGS. 17, 18, 19, and 20 (seereferences 1716, 1816, 1916, and 2016) and described below. Examples ofa VCN Data Plane are depicted in FIGS. 17, 18, 19, and 20 (seereferences 1718, 1818, 1918, and 2018) and described below. The controlplane functions include functions used for configuring a network (e.g.,setting up routes and route tables, configuring VNICs, etc.) thatcontrols how data is to be forwarded. In certain embodiments, a VCNControl Plane is provided that computes all the overlay-to-substratemappings centrally and publishes them to the NVDs and to the virtualnetwork edge devices such as various gateways such as the DRG, the SGW,the IGW, etc. Firewall rules may also be published using the samemechanism. In certain embodiments, an NVD only gets the mappings thatare relevant for that NVD. The data plane functions include functionsfor the actual routing/forwarding of a packet based upon configurationset up using control plane. A VCN data plane is implemented byencapsulating the customer's network packets before they traverse thesubstrate network. The encapsulation/decapsulation functionality isimplemented on the NVDs. In certain embodiments, an NVD is configured tointercept all network packets in and out of host machines and performnetwork virtualization functions.

As indicated above, an NVD executes various virtualization functionsincluding VNICs and VCN VRs. An NVD may execute VNICs associated withthe compute instances hosted by one or more host machines connected tothe VNIC. For example, as depicted in FIG. 2 , NVD 210 executes thefunctionality for VNIC 276 that is associated with compute instance 268hosted by host machine 202 connected to NVD 210. As another example, NVD212 executes VNIC 280 that is associated with bare metal computeinstance 272 hosted by host machine 206, and executes VNIC 284 that isassociated with compute instance 274 hosted by host machine 208. A hostmachine may host compute instances belonging to different VCNs, whichbelong to different customers, and the NVD connected to the host machinemay execute the VNICs (i.e., execute VNICs-relate functionality)corresponding to the compute instances.

An NVD also executes VCN Virtual Routers corresponding to the VCNs ofthe compute instances. For example, in the embodiment depicted in FIG. 2, NVD 210 executes VCN VR 277 corresponding to the VCN to which computeinstance 268 belongs. NVD 212 executes one or more VCN VRs 283corresponding to one or more VCNs to which compute instances hosted byhost machines 206 and 208 belong. In certain embodiments, the VCN VRcorresponding to that VCN is executed by all the NVDs connected to hostmachines that host at least one compute instance belonging to that VCN.If a host machine hosts compute instances belonging to different VCNs,an NVD connected to that host machine may execute VCN VRs correspondingto those different VCNs.

In addition to VNICs and VCN VRs, an NVD may execute various software(e.g., daemons) and include one or more hardware components thatfacilitate the various network virtualization functions performed by theNVD. For purposes of simplicity, these various components are groupedtogether as “packet processing components” shown in FIG. 2 . Forexample, NVD 210 comprises packet processing components 286 and NVD 212comprises packet processing components 288. For example, the packetprocessing components for an NVD may include a packet processor that isconfigured to interact with the NVD's ports and hardware interfaces tomonitor all packets received by and communicated using the NVD and storenetwork information. The network information may, for example, includenetwork flow information identifying different network flows handled bythe NVD and per flow information (e.g., per flow statistics). In certainembodiments, network flows information may be stored on a per VNICbasis. The packet processor may perform packet-by-packet manipulationsas well as implement stateful NAT and L4 firewall (FW). As anotherexample, the packet processing components may include a replicationagent that is configured to replicate information stored by the NVD toone or more different replication target stores. As yet another example,the packet processing components may include a logging agent that isconfigured to perform logging functions for the NVD. The packetprocessing components may also include software for monitoring theperformance and health of the NVD and, also possibly of monitoring thestate and health of other components connected to the NVD.

FIG. 1 shows the components of an example virtual or overlay networkincluding a VCN, subnets within the VCN, compute instances deployed onsubnets, VNICs associated with the compute instances, a VR for a VCN,and a set of gateways configured for the VCN. The overlay componentsdepicted in FIG. 1 may be executed or hosted by one or more of thephysical components depicted in FIG. 2 . For example, the computeinstances in a VCN may be executed or hosted by one or more hostmachines depicted in FIG. 2 . For a compute instance hosted by a hostmachine, the VNIC associated with that compute instance is typicallyexecuted by an NVD connected to that host machine (i.e., the VNICfunctionality is provided by the NVD connected to that host machine).The VCN VR function for a VCN is executed by all the NVDs that areconnected to host machines hosting or executing the compute instancesthat are part of that VCN. The gateways associated with a VCN may beexecuted by one or more different types of NVDs. For example, certaingateways may be executed by smartNICs, while others may be executed byone or more host machines or other implementations of NVDs.

As described above, a compute instance in a customer VCN may communicatewith various different endpoints, where the endpoints can be within thesame subnet as the source compute instance, in a different subnet butwithin the same VCN as the source compute instance, or with an endpointthat is outside the VCN of the source compute instance. Thesecommunications are facilitated using VNICs associated with the computeinstances, the VCN VRs, and the gateways associated with the VCNs.

For communications between two compute instances on the same subnet in aVCN, the communication is facilitated using VNICs associated with thesource and destination compute instances. The source and destinationcompute instances may be hosted by the same host machine or by differenthost machines. A packet originating from a source compute instance maybe forwarded from a host machine hosting the source compute instance toan NVD connected to that host machine. On the NVD, the packet isprocessed using a packet processing pipeline, which can includeexecution of the VNIC associated with the source compute instance. Sincethe destination endpoint for the packet is within the same subnet,execution of the VNIC associated with the source compute instanceresults in the packet being forwarded to an NVD executing the VNICassociated with the destination compute instance, which then processesand forwards the packet to the destination compute instance. The VNICsassociated with the source and destination compute instances may beexecuted on the same NVD (e.g., when both the source and destinationcompute instances are hosted by the same host machine) or on differentNVDs (e.g., when the source and destination compute instances are hostedby different host machines connected to different NVDs). The VNICs mayuse routing/forwarding tables stored by the NVD to determine the nexthop for the packet.

For a packet to be communicated from a compute instance in a subnet toan endpoint in a different subnet in the same VCN, the packetoriginating from the source compute instance is communicated from thehost machine hosting the source compute instance to the NVD connected tothat host machine. On the NVD, the packet is processed using a packetprocessing pipeline, which can include execution of one or more VNICs,and the VR associated with the VCN. For example, as part of the packetprocessing pipeline, the NVD executes or invokes functionalitycorresponding to the VNIC (also referred to as executes the VNIC)associated with source compute instance. The functionality performed bythe VNIC may include looking at the VLAN tag on the packet. Since thepacket's destination is outside the subnet, the VCN VR functionality isnext invoked and executed by the NVD. The VCN VR then routes the packetto the NVD executing the VNIC associated with the destination computeinstance. The VNIC associated with the destination compute instance thenprocesses the packet and forwards the packet to the destination computeinstance. The VNICs associated with the source and destination computeinstances may be executed on the same NVD (e.g., when both the sourceand destination compute instances are hosted by the same host machine)or on different NVDs (e.g., when the source and destination computeinstances are hosted by different host machines connected to differentNVDs).

If the destination for the packet is outside the VCN of the sourcecompute instance, then the packet originating from the source computeinstance is communicated from the host machine hosting the sourcecompute instance to the NVD connected to that host machine. The NVDexecutes the VNIC associated with the source compute instance. Since thedestination end point of the packet is outside the VCN, the packet isthen processed by the VCN VR for that VCN. The NVD invokes the VCN VRfunctionality, which may result in the packet being forwarded to an NVDexecuting the appropriate gateway associated with the VCN. For example,if the destination is an endpoint within the customer's on-premisenetwork, then the packet may be forwarded by the VCN VR to the NVDexecuting the DRG gateway configured for the VCN. The VCN VR may beexecuted on the same NVD as the NVD executing the VNIC associated withthe source compute instance or by a different NVD. The gateway may beexecuted by an NVD, which may be a smartNIC, a host machine, or otherNVD implementation. The packet is then processed by the gateway andforwarded to a next hop that facilitates communication of the packet toits intended destination endpoint. For example, in the embodimentdepicted in FIG. 2 , a packet originating from compute instance 268 maybe communicated from host machine 202 to NVD 210 over link 220 (usingNIC 232). On NVD 210, VNIC 276 is invoked since it is the VNICassociated with source compute instance 268. VNIC 276 is configured toexamine the encapsulated information in the packet, and determine a nexthop for forwarding the packet with the goal of facilitatingcommunication of the packet to its intended destination endpoint, andthen forward the packet to the determined next hop.

A compute instance deployed on a VCN can communicate with variousdifferent endpoints. These endpoints may include endpoints that arehosted by CSPI 200 and endpoints outside CSPI 200. Endpoints hosted byCSPI 200 may include instances in the same VCN or other VCNs, which maybe the customer's VCNs, or VCNs not belonging to the customer.Communications between endpoints hosted by CSPI 200 may be performedover physical network 218. A compute instance may also communicate withendpoints that are not hosted by CSPI 200, or are outside CSPI 200.Examples of these endpoints include endpoints within a customer'son-premise network or data center, or public endpoints accessible over apublic network such as the Internet. Communications with endpointsoutside CSPI 200 may be performed over public networks (e.g., theInternet) (not shown in FIG. 2 ) or private networks (not shown in FIG.2 ) using various communication protocols.

The architecture of CSPI 200 depicted in FIG. 2 is merely an example andis not intended to be limiting. Variations, alternatives, andmodifications are possible in alternative embodiments. For example, insome implementations, CSPI 200 may have more or fewer systems orcomponents than those shown in FIG. 2 , may combine two or more systems,or may have a different configuration or arrangement of systems. Thesystems, subsystems, and other components depicted in FIG. 2 may beimplemented in software (e.g., code, instructions, program) executed byone or more processing units (e.g., processors, cores) of the respectivesystems, using hardware, or combinations thereof. The software may bestored on a non-transitory storage medium (e.g., on a memory device).

FIG. 4 depicts connectivity between a host machine and an NVD forproviding I/O virtualization for supporting multitenancy according tocertain embodiments. As depicted in FIG. 4 , host machine 402 executes ahypervisor 404 that provides a virtualized environment. Host machine 402executes two virtual machine instances, VM1 406 belonging tocustomer/tenant #1 and VM2 408 belonging to customer/tenant #2. Hostmachine 402 comprises a physical NIC 410 that is connected to an NVD 412via link 414. Each of the compute instances is attached to a VNIC thatis executed by NVD 412. In the embodiment in FIG. 4 , VM1 406 isattached to VNIC-VM1 420 and VM2 408 is attached to VNIC-VM2 422.

As shown in FIG. 4 , NIC 410 comprises two logical NICs, logical NIC A416 and logical NIC B 418. Each virtual machine is attached to andconfigured to work with its own logical NIC. For example, VM1 406 isattached to logical NIC A 416 and VM2 408 is attached to logical NIC B418. Even though host machine 402 comprises only one physical NIC 410that is shared by the multiple tenants, due to the logical NICs, eachtenant's virtual machine believes they have their own host machine andNIC.

In certain embodiments, each logical NIC is assigned its own VLAN ID.Thus, a specific VLAN ID is assigned to logical NIC A 416 for Tenant #1and a separate VLAN ID is assigned to logical NIC B 418 for Tenant #2.When a packet is communicated from VM1 406, a tag assigned to Tenant #1is attached to the packet by the hypervisor and the packet is thencommunicated from host machine 402 to NVD 412 over link 414. In asimilar manner, when a packet is communicated from VM2 408, a tagassigned to Tenant #2 is attached to the packet by the hypervisor andthe packet is then communicated from host machine 402 to NVD 412 overlink 414. Accordingly, a packet 424 communicated from host machine 402to NVD 412 has an associated tag 426 that identifies a specific tenantand associated VM. On the NVD, for a packet 424 received from hostmachine 402, the tag 426 associated with the packet is used to determinewhether the packet is to be processed by VNIC-VM1 420 or by VNIC-VM2422. The packet is then processed by the corresponding VNIC. Theconfiguration depicted in FIG. 4 enables each tenant's compute instanceto believe that they own their own host machine and NIC. The setupdepicted in FIG. 4 provides for I/O virtualization for supportingmulti-tenancy.

FIG. 5 depicts a simplified block diagram of a physical network 500according to certain embodiments. The embodiment depicted in FIG. 5 isstructured as a Clos network. A Clos network is a particular type ofnetwork topology designed to provide connection redundancy whilemaintaining high bisection bandwidth and maximum resource utilization. AClos network is a type of non-blocking, multistage or multi-tieredswitching network, where the number of stages or tiers can be two,three, four, five, etc. The embodiment depicted in FIG. 5 is a 3-tierednetwork comprising tiers 1, 2, and 3. The TOR switches 504 representTier-0 switches in the Clos network. One or more NVDs are connected tothe TOR switches. Tier-0 switches are also referred to as edge devicesof the physical network. The Tier-0 switches are connected to Tier-1switches, which are also referred to as leaf switches. In the embodimentdepicted in FIG. 5 , a set of “n” Tier-0 TOR switches are connected to aset of “n” Tier-1 switches and together form a pod. Each Tier-0 switchin a pod is interconnected to all the Tier-1 switches in the pod, butthere is no connectivity of switches between pods. In certainimplementations, two pods are referred to as a block. Each block isserved by or connected to a set of “n” Tier-2 switches (sometimesreferred to as spine switches). There can be several blocks in thephysical network topology. The Tier-2 switches are in turn connected to“n” Tier-3 switches (sometimes referred to as super-spine switches).Communication of packets over physical network 500 is typicallyperformed using one or more Layer-3 communication protocols. Typically,all the layers of the physical network, except for the TORs layer aren-ways redundant thus allowing for high availability. Policies may bespecified for pods and blocks to control the visibility of switches toeach other in the physical network so as to enable scaling of thephysical network.

A feature of a Clos network is that the maximum hop count to reach fromone Tier-0 switch to another Tier-0 switch (or from an NVD connected toa Tier-0-switch to another NVD connected to a Tier-0 switch) is fixed.For example, in a 3-Tiered Clos network at most seven hops are neededfor a packet to reach from one NVD to another NVD, where the source andtarget NVDs are connected to the leaf tier of the Clos network.Likewise, in a 4-tiered Clos network, at most nine hops are needed for apacket to reach from one NVD to another NVD, where the source and targetNVDs are connected to the leaf tier of the Clos network. Thus, a Closnetwork architecture maintains consistent latency throughout thenetwork, which is important for communication within and between datacenters. A Clos topology scales horizontally and is cost effective. Thebandwidth/throughput capacity of the network can be easily increased byadding more switches at the various tiers (e.g., more leaf and spineswitches) and by increasing the number of links between the switches atadjacent tiers.

In certain embodiments, each resource within CSPI is assigned a uniqueidentifier called a Cloud Identifier (CID). This identifier is includedas part of the resource's information and can be used to manage theresource, for example, via a Console or through APIs. An example syntaxfor a CID is:

-   -   ocid1.<RESOURCE TYPE>.<REALM>.[REGION][.FUTURE USE].<UNIQUE ID>        where,        ocid1: The literal string indicating the version of the CID;        resource type: The type of resource (for example, instance,        volume, VCN, subnet, user, group, and so on);        realm: The realm the resource is in. Example values are “c1” for        the commercial realm, “c2” for the Government Cloud realm, or        “c3” for the Federal Government Cloud realm, etc. Each realm may        have its own domain name;        region: The region the resource is in. If the region is not        applicable to the resource, this part might be blank;        future use: Reserved for future use.        unique ID: The unique portion of the ID. The format may vary        depending on the type of resource or service.        Packet Flow Control

FIG. 6 illustrates an example of network boundaries 600 according tocertain embodiments. Generally, a network boundary can represent alogical construct and/or a physical construct of a boundary of a virtualand/or a substrate network, where the flow of packets within thisboundary can be controlled. For example, a network boundary cancorrespond to a particular VCN or portion thereof that is hosted on asubstrate network within a particular geographical region. Furthermore,a network boundary can be selected by a customer to control the packetflow from and/or to the customer's network(s). Even if multiplecustomers select the same network boundary, their selection is in effectspecific to their configured networks and correspond to differentlogical and/or physical constructs. For example, if two customers selecta VCN network boundary, their traffic flows are in effect controlledaccording to their respective VCNs.

In the illustration of FIG. 6 , six network boundaries 600 are shown. Afirst network boundary corresponds to an L2 VLAN within a VCN of acustomer. The customer can select this network boundary to indicate thatpackets (or, more accurately, frames) can flow between compute instancesof the customer's L2 VLAN. A second boundary corresponds to an L3 subnetwithin the VCN. The customer can select this network boundary toindicate that packets can flow between compute instances of thecustomer's L2 subnet. The L2 VLAN network boundary and the L3 subnetnetwork boundary are not mutually exclusive. Further, multiple L2 VLANnetwork boundaries and/or multiple L3 subnet network boundaries withinthe VCN can be selected by the customer.

A third network boundary corresponds to the VCN. The customer can selectthis network boundary to indicate that packets can flow between computeinstances of the VCN. A fourth network boundary corresponds to a privatenetwork of the customer, such as an on-premise network. A selection ofthis network boundary expands the flow such that packets can be sentbetween the VCN and the private network. A fifth network boundarycorresponds to a peered VCN of the customer (e.g., a second VCN peeredwith a first VCN that corresponds to the third network boundary). Aselection of this network boundary expands the flow such that packetscan be sent between the peered VCNs. A sixth network boundarycorresponds to a public network, such as the Internet (e.g., a secondVCN peered with a first VCN that corresponds to the third networkboundary). The customer can select this network boundary to indicatethat packets can flow between its compute instances and resources on thepublic network.

FIG. 6 illustrates a concentric distribution of the network boundaries600 to indicate that a network boundary shown by a larger circle caninclude network boundary(ies) shown by the smaller circle(s). However,the embodiments of the present disclosure are not limited as such.Network boundaries can be inclusive, exclusive, or mutually exclusive.For example, the customer can select an L3 subnet network boundary and apeered VCN boundary. In this example, packet flows are permitted betweencompute instances of the L3 subnet and between compute instances of theL3 subnet and compute instances of the peered VCN. However, packet flowsare prohibited between the compute instances of the L3 subnet and othercompute instances of the VCN.

FIG. 7 illustrates an example of packet flow rules 700 according tocertain embodiments. Generally, upon a customer selection of a set ofnetwork boundaries, a packet flow rule can be generated specifying thatpacket flows within the selected set are permitted, and are otherwiseprohibited. The packet flow rule can be used to generate scoping data,where this scoping data indicates the permitted network boundary(ies)and/or prohibited network boundary(ies). The customer's selection can begranular to a specific compute instance within a selected networkboundary. The selection can be global to all compute instances within aselected network boundary or the selection can be at any resolutionlevel between the two. Regardless, a packet flow rule can be generatedper compute instance to which it applies.

In the illustration of FIG. 7 , the customer has selected the VCNnetwork boundary. This selection is shown by marking the outer networkboundaries (e.g., the ones corresponding to private network, peered VCN,and public network) with horizontal lines/pattern. Of course otherselections are possible and result in different packet flow rules. Giventhe illustrated selection, the packet flow rules 700 indicate apermitted egress/ingress flow 710 between any computing instances withinthe VCN and a prohibited egress/ingress flow 720 between a computeinstance within the VCN and a resource outside of the VCN (e.g., theresource is not a compute instance hosted in the VCN).

As explained herein above, a packet flow rule can be defined per computeinstance of the VCN. This packet flow rule may control the ingress andegress flows in the same manner. However, the embodiments of the presentdisclosure are not limited as such. In particular, the ingress andegress flows can be controlled differently. For instance, a first packetflow rule can be generated for a compute instance of a VCN to indicatethat packets sent from the compute instance can cross a certain networkboundary (e.g., the compute instance can send packets to a computeinstance in a peered VCN). A second packet flow rule can be generatedfor the compute instance to indicate that packets sent to the computeinstance can be dropped when they originate from outside a certainnetwork boundary (e.g., the compute instance receives packets from othercompute instances within the VCN but not from compute instances withinthe peered VCN).

FIG. 8 illustrates an example of a packet structure 800 of a packet,where this structure 800 includes scoping data 830 indicating a packetflow rule according to certain embodiments. Generally, the scoping data830 encodes the packet flow rule such that, as the packet flows along anetwork path, processing resources along this path can determine andenforce the packet rule based on the scoping data.

In an example, the packet structure 800 includes a header 810 and apayload 820. The header 810 is usable to determine how the packet is tobe processed (e.g., by including a source address, a destinationaddress, a protocol identifier, and/or encapsulation data among otherinformation such that the packet can be routed between virtual networksor within a virtual network and via one or more substrate networks). Thepayload 820 includes the data that is sent from a source (e.g., from acompute instance within a virtual network).

The scoping data 830 indicates a scope of the packet's flow, such aswhat network boundary can the packet flow within, what network boundarycan the packet cross, and/or what network boundary can the packet notcross. The scoping data 830 can be included as metadata in the header810, where the metadata indicates that a flow within a network boundaryis permitted and/or a flow within another network boundary isprohibited. For example and referring back to the illustration of FIG. 7, the metadata indicates that the packet can flow within the VCN.Additionally or alternatively, the metadata indicates that the packetcannot flow outside of the VCN.

In an example, the scoping data 830 is included as a field in the header810, where this field indicates network boundary identifier(s) 832 andpermission(s)/prohibitions 834 related to the network boundaryidentifier(s) 832. For instance, the field can be a byte long. A firstbit (e.g., the most significant bit) can indicate whether the packetstructure 800 supports or includes scoping data (e.g., set to “1” toindicate the support and to “0” otherwise). The remaining seven bits canbe used to indicate the permitted network boundaries. In particular, 2⁷selectable combinations of permitted network boundaries are possible. Inanother illustration, the bits in the field form a bit mask. Each bit inthe bit mask corresponds to a network boundary and its binary valuerepresents the permission or prohibition (e.g., “1” indicatespermission, “0” indicated otherwise).

FIG. 9 illustrates an example of a method for controlling a packet flowaccording to certain embodiments. The method includes, at operation 902,defining a packet flow rule. The packet flow rule can depend on aselection of a network boundary from multiple network boundariesavailable to the customer, where the network boundaries can be similarto the ones described in FIGS. 6-7 . The definition of the networkpacket rule reflects the customer's selection, as further illustrated inFIGS. 10-11 . The method also includes, at operation 904, adding scopingdata to a packet generated by a compute instance based on a packet flowrule defined for the compute instance. The packet can have a packetstructure such as the one illustrated in FIG. 8 . The scoping data canbe included in a header of the packet, as further described in FIGS.12-13 . The method also includes, at operation 906, enforcing the packetrule based on the scoping data. A processing resource can receive thepacket, extract the scoping data, identify the permitted networkboundary(ies) based on the scoping data, determine whether the packetcan be sent (e.g., if its destination or the next hop is within thepermitted network boundary(ies)), and send or drop the packet based onthe determination, as further described in FIGS. 14-16 .

FIG. 10 illustrates an example of a system for generating a packet flowrule according to certain embodiments. As illustrated, the systemincludes a host machine 1010 and an NVD 1020, such as a smartNIC. TheNVD 1020 receives customer data 1030 from a control plane (not shown),where the customer data 1030 indicates a selection of a set of networkboundaries for controlling packet flows. The NVD 1020 generates andstores packet flow rules based on the customer data 1030.

Generally, the host machine 1010 hosts one or more compute instances1012 of a customer and is connected with the NVD 120. The connection canbe an Ethernet link. The NVD 120 hosts, among other virtual functions,one or more VNICs 1022, each of which is associated with one of thecompute instances 1012 and provides virtual network interface functionsto the compute instance. The virtual network interface functions includeproviding an interface to a virtual network.

In an example, the control plane receives input of the customer via anapplication programing interface (API) or some other means. The inputindicates a selection of a network boundary within which packet flowsare permitted. The selection can be specific to one of the computeinstances 1012, can be generic to all compute instances 1012, or canindicate a subset of the compute instances 1012. In all three cases, thecontrol plane sends the customer data 1030 to the NVD 1020 indicatingthe network boundary and the compute instance(s) to which the customerdata 1030 applies. The customer data 103 can be sent as a configurationfile. In turn, the NVD 1020 determines the affected compute instance(s).For each affected compute instance, the NVD 1020 generates a packet flowrule 1024 indicating the permitted network boundary and/or a prohibitednetwork boundary. For instance the packet flow rule 1024 identifies anetwork boundary and the permission or prohibition related thereto. TheNVD 1020 also determines the VNIC that is associated with the computeinstance and stores, in association with the VNIC, the packet flow rule1024. For instance, the packet flow rule 1024 is stored in a cacheusable by the VNIC. Of course, multiple packet flow rules can besimilarly generated and stored, one for each affected compute instance.In addition, each packet flow rule can indicate multiple permittednetwork boundaries and/or multiple prohibited network boundaries.

Although FIG. 10 illustrates that an NVD that is directly connected to ahost machine generates a packet flow rule for a compute instance of thehost machine, other devices may additionally or alternatively be used togenerate such a packet flow rule. Such devices need not be directlyconnected to the host machine. For instance, and referring back to FIG.10 , the NVD 1020 may host a lightweight version of a VNIC and may beconnected, via a tunnel or some other peering mechanism, to a serverfleet. The server fleet can be a set or an enclave of servers or hostmachines that hosts a network interface service for one or morecustomers, where this service provides network interface functions forconnectivity between computer instances. In one example, the networkinterface service can be a VNIC as a service (VNICaaS). In this example,the network interface service includes multiple VNICS and these VNICscan be referred to as service VNICs (as opposed to micro-VNICs).Typically a service VNIC can be associated with multiple micro-VNICs,each of which is in turn associated with a single compute instance. Inother words, a service VNIC can be associated with multiple computeinstances through their corresponding micro-VNICs and can providevirtual network interface functions to these compute instances. Thevirtual network interface functions include providing an interface of acompute instance to a virtual network. In this example, the server fleet(e.g., one or more of the servers) can generate a packet flow rule for acompute instance and can store the packet flow for use by a service VNICassociated with the compute instance.

FIG. 11 illustrates an example of a method for generating a packet flowrule according to certain embodiments. Operations of the method areillustrated as being performed by a network virtualization device. Thisdevice can be similar to the NVD 1020 of FIG. 10 , a server fleet thatprovides a network interface service, or another device of a cloudinfrastructure that provides virtualization services (e.g., a router, agateway, a switch, a load balancer, etc.). Some or all of theinstructions for performing the operations can be implemented ashardware circuitry and/or stored as computer-readable instructions on anon-transitory computer-readable medium of the network virtualizationdevice. As implemented, the instructions represent modules that includecircuitry or code executable by processors of the network virtualizationdevice. The use of such instructions configures the networkvirtualization device to perform the specific operations describedherein. Each circuitry or code in combination with the relevantprocessor(s) represents a means for performing a respectiveoperation(s). While the operations are illustrated in a particularorder, it should be understood that no particular order is necessary andthat one or more operations may be omitted, skipped, performed inparallel, and/or reordered.

In an example, the method starts at operation 1102, where the networkvirtualization device receives customer data 1102. For instance, thecustomer data 1102 is received from a control plane and indicates acustomer's selection of a network boundary to use for controlling packetflows (or multiple selected network boundaries as described in FIG.). Atoperation 1104, the network virtualization device determines a selectednetwork boundary(ies). For instance, the selected network boundary(ies)is identified from the customer data, where the customer data indicatesthat the packet flow is permitted within the boundary(ies) and/orprohibited within other network boundary(ies). At operation, 1106, thenetwork virtualization device determines the affected customerinstance(s). The customer's selection may be applicable more than thecompute instance. If so, the customer data indicates the affectedcustomer instances. Otherwise, the customer data indicates the onlyaffected customer instance. At operation 1108, the networkvirtualization device generates, per affected compute instance, a packetflow rule. The packet flow generated for a compute indicates how thepacket flows from or to the compute instance are to be controlled giventhe permitted and/or prohibited network boundary(ies). At operation1110, the network virtualization device stores each packet flow ruleassociated with the corresponding compute instance. For instance, thenetwork virtualization device may host a VNIC that is associated with acompute instance. The packet flow rule corresponding to the computeinstance can be stored in a cache usable by the VNIC.

FIG. 12 illustrates an example of a system for generating a packet thatincludes data indicating a packet flow rule according to certainembodiments. The system includes a host machine 1210 and an NVD 1220similar to the host machine 1010 and NVD 1020, respectively, of FIG. 10. The host machine 1210 hosts a compute instance 1212 of a customer,whereas the NVD 1220 hosts a VNIC 1222 associated with the computeinstance 1212, and stores a packet flow rule 1224 usable to control thepacket flow from the compute instance 1212.

In operation, the compute instance 1212 sends a packet that includes aheader 1214 and a payload 1216. The packet is sent over the link (e.g.,Ethernet link) from the host machine 1210 to the NVD 1220. The NVD 1220determines, from the header 1214, that this packet is sent from thecompute instance 1212. In an example, the NVD 1220 also determines fromthe packet flow rule 1224 the permitted network boundary(ies) and/orprohibited network boundary(ies) for the flow of the packet from thecompute instance 1212. If the flow is permitted, the NVD 1220 generatesscoping data indicating the scope of the flow. Otherwise, the NVD 1220drops the packet. In another example, the VNIC 1222 performs thisdetermination and, as applicable, generates the scoping data. In bothexamples, the scoping data is included in an updated header 1226 of thepacket. The NVD 1220 outputs the packet with the updated header 1226 andthe payload 1216 onto a substrate network, whereby the updated header1226 further includes encapsulation data for sending the packet throughthe substrate network. As illustrated in FIG. 12 , the updated header1126 includes an overlay header 1227 and a scoping field 1229. Theoverlay header 1227 includes the encapsulation data. The scoping field1129 includes the scoping data in a similar way as the description ofthe scoping data 830 in FIG. 8 .

To illustrate, consider a first example, where the compute instance 1212is within a VCN of the customer, and where the packet flow rule 1224permits the flow of packets from the compute instance 1212 to any othercompute instance within the VCN only. The NVD 1120 receives the packetof the compute instance and determines, using a VCN mapping table, thata destination tunnel endpoint is within the permitted network boundary.Accordingly, the NVD 1220 adds the scoping data and other encapsulationdata to the packet and sends the packet forward.

To illustrate, consider a first example, where the compute instance 1212is within a VCN of the customer, and where the packet flow rule 1224permits the flow of packets from the compute instance 1212 to any othercompute instance within the VCN only. In this example, the computeinstance 1212 sends a packet destined to a compute instance within theVCN. The NVD 1220 receives and determines, using a VCN mapping table,that a destination tunnel endpoint is within the permitted networkboundary. Accordingly, the NVD 1220 adds the scoping data and otherencapsulation data to the packet and sends the packet forward.

In a second example, the packet flow rule 1124 also permits the flow ofpackets to the VCN only, but the compute instance 1212 sends a packetdestined to a resource outside of the VCN. In this example, the NVD 1220receives and determines, using the VCN mapping table, that a destinationtunnel endpoint is outside of the permitted network boundary.Accordingly, the NVD 1220 drops the packet.

In a third example, the packet flow rule 1124 permits the flow ofpackets to an on-premise network of the customer, where a DRG couplesthe VCN with the on-premise network. In this example, a packet isdestined to an endpoint within the on-premise network. The NVD 1220receives and determines, using a VCN mapping table, that the destinationis outside of the VCN. Next, the NVD 1220 determines, using a routingtable, that the packet is to be sent to the DRG. Because the DRG iswithin the permitted network boundary, the NVD 1220 adds the scopingdata and other encapsulation data to the packet and sends the packetforward.

In FIG. 12 , a NVD that is directly coupled with a host machine (e.g., aSmartNIC) generates and adds scoping data to a packet based on a packetflow rule. However, the embodiments are not limited to this type ofNVDs. Instead, the embodiments similarly apply to other devices of thesubstrate network or a virtual network, such as to a server fleet thatprovides a network interface service (e.g., VNICaaS), a router, aswitch, a gateway, load balancer, and the like. For instance, an NVD ofthe service fleet may receive a packet of the compute instance 1212 fromthe NVD 1220 and may, in turn, determine the applicable packet flow ruleand either drop the packet or generate and add the relevant scopingdata. In another illustration, an ingress packet may be received by, forinstance, a router and may not include scoping data. The router maydetermine that the packet is destined to a compute instance and may addscoping data based on a packet flow rule applicable to the computeinstance.

FIG. 13 illustrates an example of a method for generating a packet thatincludes data indicating a packet flow according to certain embodiments.Operations of the method are illustrated as being performed by a networkvirtualization device. This device can be similar to the NVD 1220 ofFIG. 12 , a server fleet that provides a network interface service, oranother device of a cloud infrastructure that provides virtualizationservices (e.g., a router, a gateway, a switch, a load balancer, etc.).Some or all of the instructions for performing the operations can beimplemented as hardware circuitry and/or stored as computer-readableinstructions on a non-transitory computer-readable medium of the networkvirtualization device. As implemented, the instructions representmodules that include circuitry or code executable by processors of thenetwork virtualization device. The use of such instructions configuresthe network virtualization device to perform the specific operationsdescribed herein. Each circuitry or code in combination with therelevant processor(s) represents a means for performing a respectiveoperation(s). While the operations are illustrated in a particularorder, it should be understood that no particular order is necessary andthat one or more operations may be omitted, skipped, performed inparallel, and/or reordered.

In an example, the method starts at operation 1302, where the networkvirtualization device receives a packet of a compute instance. Forinstance, the packet is generated by the compute instance, is sent by ahost machine of the compute instance, and is received by the NVD over alink with the host machine. At operation 1304, the networkvirtualization device determines a VNIC that is associated with thecompute instance. For instance, the network virtualization deviceidentifies the compute instance based on a source address in the headerof the packet and identifies, from a plurality of VNICs hosted by thenetwork virtualization device, the VNIC that is associated with thecompute instance. At operation 1306, the network virtualization devicedetermines a packet flow rule associated with the VNIC. For instance,the packet flow rule is stored in the cache of the VNIC 1 and indicatesa permitted network boundary(ies) and/or a prohibited networkboundary(ies) for packet flows from the compute instance. At operation1308, the network virtualization device determines whether the flow ofthe packet is permitted or prohibited. For instance, using mappingtables, routing tables, and/or other configuration information of asubstrate network and/or virtual network, the network virtualizationdevice determines whether a destination of the packet is within apermitted boundary. The destination may be the addressed destination inthe packet or a next hop destination. If permitted, the operation 1310follows operation 1308. Otherwise, operation 1320 is performed, wherethe network virtualization device drops the packet. At operation 1310,the network virtualization device generates scoping data based on thepacket flow rule. For instance, the scoping data can indicate thenetwork boundary(ies) and the related permission(s)/prohibition(s). Atoperation 1312, the network virtualization device includes the scopingdata in the header of the packet. For instance, the scoping data areadded as bits in a scoping field, within the header as described in FIG.8 . At operation 1314, the network virtualization device sends thepacket. For instance, the network virtualization device furtherencapsulates the packet and sends the encapsulated packet on thesubstrate network.

FIG. 14 illustrates an example of a system for enforcing a packet flowrule indicated in scoping data of a packet according to certainembodiments. The system includes a host machine 1410 and an NVD 1420similar to the host machine 1010 and NVD 1020, respectively, of FIG. 10. The host machine 1410 hosts a compute instance 1412 of a customer,whereas the NVD 1420 hosts a VNIC 1422 associated with the computeinstance 1412. In the example of FIG. 14 , the packet flow is ingress,where the packet is received by the network virtualization device 1420and a decision is made as to whether the packet is to be sent to thecompute instance 1412.

In operation, the NVD 1420 receives the packet from a substrate network(e.g., from a switch of the substrate network). In an example, thepacket has a similar structure as the packet structure 800 and includesa header 1426 and a payload 1416. The header 1426 encapsulates anoverlay header 1427 (for the flow of the packet on the substratenetwork) and a scoping field 1429 that encodes the scoping data. Thescoping data indicates a network boundary(ies) within which the packetis permitted or prohibited to flow. Based on a determination that thedestination of the packet is the compute instance 1412, the NVD 1420(or, similarly, the VNIC) determines whether the compute instance 1412falls within a permitted network boundary. If not, the packet isdropped. Otherwise, the header 1426 is updated (shown in FIG. 14 as anupdated header 1414), where the update includes removing the overlayheader 1427 and the scoping field 1429. The packet (including theupdated header 1414 and the payload 1416) is sent to the computeinstance 1412 via the host machine 1410.

To illustrate, consider a first example of the compute instance 1412being within a VCN of the customer and the scoping data indicating thatthe packet can flow within the VCN. In this case, the NVD 1420 (or,similarly, the VNIC 1422) determines that the permitted network boundarycorresponds to the VCN and, accordingly, sends the packet to the computeinstance 1412. In a second example, the compute instance 1412 belongs toa first L3 subnet of the VCN. In this example, the scoping dataindicates that the packet can flow to a second L3 subnet of the VCNonly. Here, the NVD 1420 (or, similarly, the VNIC 1422) determines thatthe permitted network boundary excludes the first L3 subnet, and,accordingly, drops the packet.

In FIG. 14 , a NVD that is directly coupled with a host machine (e.g., aSmartNIC) uses scoping data to enforce a packet flow rule before apacket is sent to a compute instance of the host machine. However, theembodiments are not limited to ingress traffic and this type of NVD.Instead, the embodiments similarly apply to egress traffic and/or otherdevices of the substrate network or a virtual network as furtherdescribed in FIG. 15 .

FIG. 15 illustrates another example of a system for enforcing a packetflow rule indicated in scoping data of a packet according to certainembodiments. The system includes a first NVD 1520 and a second NVD 1530coupled via a substrate network. In the interest of clarity ofexplanation, a packet flow is described, where a packet is sent from thefirst NVD 1520 to the second NVD 1530. However, the packet flow can bein the opposite direction as indicated by the double arrows in FIG. 15 .

In an example, the first NVD 1520 hosts a VNIC 1522 associated with acompute instance of a customer (e.g., the NVD 1520 is a SmartNIC). Thecompute machine belongs to a VCN of the customer and is executing on ahost machine, where the host machine is coupled with the first NVD 1520via the substrate network. The second NVD 1530 hosts a virtual gateway1532 (e.g., a DRG) that couples the customer's VCN to another network(e.g., another peered VCN, an on-premise network, and/or or a publicnetwork). The VNIC 1522 and the virtual gateway 1532 are describedherein for illustrative purposes only and the embodiments of the presentdisclosure are not limited as such. Instead, the embodiments similarlyapply to any other virtual network functions that can be hosted on thefirst NVD 1520 and/or the second NVD 1530, such as a router, a switch, aload balancer, and the like.

In operation, the first NVD 1520 sends a packet to the second NVD 1530via the substrate network (or, similarly, the VNIC 1522 sends the packetto the virtual gateway via a virtual network). The packet has a packetstructure similar to the packet structure 800 of FIG. 8 and includes aheader 1526 and a payload 1516. The header 1526 encapsulates an overlayheader 1527 (for the flow of the packet on the substrate network) and ascoping field 1529 that encodes the scoping data. The scoping dataindicates a network boundary(ies) within which the packet is permittedor prohibited to flow. In turn, the second NVD 1530 receives andprocesses the packet. The processing includes, among other things,extracting the scoping data from the scoping field 1529 and determining,based on the extracted scoping data, the permitted and/or prohibitednetwork boundary(ies). Based on mapping tables, routing tables, and/orother network configuration information, the second NVD 1530 (or,similarly, the virtual gateway 1532) determines whether a destination ofthe packet is within a permitted boundary. The destination may be theaddressed destination in the packet or a next hop destination. Ifprohibited, the second VND 1530 drops the packet. Otherwise, the secondNVD 1530 sends the packet on the substrate network (or, similarly, thevirtual gateway 1532 sends the packet on the virtual network). Here, theheader 1526 may be updated (shown as an updated header 1536), where theupdate can include updates to the encapsulation data (e.g., an updatedoverlay header 1537) such that the packet can flow forward. The updatedheader 1536 may include the same scoping field 1529 (e.g., the scopingdata is not updated), such that the scoping data can travel with thepacket.

To illustrate, consider a first example, where the packet flow ruleassociated with the compute instance permits the flow of packets to apeered VCN of the customer, but not to an on-premise network of thecustomer, where a DRG hosted by the second NVD 1530 couples the VCN withthe peered VCN and the on-premise network. In this example, the computeinstance generates a packet that is destined to a second computeinstance within the peered VCN. The first NVD 1220 receives the packet,updates its header to include the scoping data, and sends the packet tothe second NVD 1530. In turn, the second NVD 1530 (or, similarly, theDRG) determines that the destination is within the peered VCN.Accordingly, the NVD 1530 (or, similarly, the DRG) sends the packetforward. In a second example, the compute instance generates a packetthat is destined to an endpoint within the on-premise network. Hereinstead, upon receiving the packet from the first NVD 1520, the secondNVD 1530 (or, similarly, the DRG) determines that the packet will flowoutside the permitted network boundaries (e.g., the VCN and the peeredVCN). Accordingly, the second NVD 1530 drops this packet.

FIG. 16 illustrates an example of a method for enforcing a packet flowrule indicated in scoping data of a packet information according tocertain embodiments. Operations of the method are illustrated as beingperformed by a network virtualization device, such as the NVD 1520 orthe NVD 1530 of FIG. 15 . Some or all of the instructions for performingthe operations can be implemented as hardware circuitry and/or stored ascomputer-readable instructions on a non-transitory computer-readablemedium of the network virtualization device. As implemented, theinstructions represent modules that include circuitry or code executableby processors of the network virtualization device. The use of suchinstructions configures the network virtualization device to perform thespecific operations described herein. Each circuitry or code incombination with the relevant processor(s) represents a means forperforming a respective operation(s). While the operations areillustrated in a particular order, it should be understood that noparticular order is necessary and that one or more operations may beomitted, skipped, performed in parallel, and/or reordered.

In an example, the method starts at operation 1602, where the networkvirtualization device receives a packet of a compute instance. Forinstance, the packet is generated by the compute instance and is eitherreceived directly from the host machine of the compute instance (e.g.,in the case where the network virtualization device hosts a VNIC for thecompute instance) or indirectly therefrom (e.g., in the case where thenetwork virtualization device hosts a VNIC as a service for one or morecompute instances, a router, a switch, a gateway, a load balancer, orthe like). The packet's header can include scoping data by, forinstance, having the data structure 800 of FIG. 8 . At operation 1604,the network virtualization device determines the scoping data from theheader of the packet. For instance, the scoping data is extracted from ascoping field of the header and indicates a network boundary(ies) withinwhich the packet is permitted and/or prohibited to flow. At operation1606, the network virtualization device determines a flow of the packet.For instance, this is a forward looking determination. In particular,the network virtualization device determines where the packet would besent (e.g., a final destination or a next network hop) based on headerinformation of the packet, mapping tables, routing tables, and/ornetwork configuration information. At operation 1608, the networkvirtualization device determines whether the packet flow is permitted ornot. For instance, if the destination (final destination or next hopdestination) is within a permitted network boundary, the flow isdetermined to be permitted and operation 1610 follows operation 1608.Otherwise, the flow is not permitted and operation 1620 followsoperation 1608. At operation 1610, the flow is permitted and,accordingly, the network virtualization device sends the packet forward.For instance, the network virtualization device updates the headerinformation (e.g., by revising the encapsulation data as needed) andsends the packet to the destination. At operation 1620, the flow isprohibited and, accordingly, the network virtualization device drops thepacket.

Example Infrastructure as a Service Architectures

As noted above, infrastructure as a service (IaaS) is one particulartype of cloud computing. IaaS can be configured to provide virtualizedcomputing resources over a public network (e.g., the Internet). In anIaaS model, a cloud computing provider can host the infrastructurecomponents (e.g., servers, storage devices, network nodes (e.g.,hardware), deployment software, platform virtualization (e.g., ahypervisor layer), or the like). In some cases, an IaaS provider mayalso supply a variety of services to accompany those infrastructurecomponents (e.g., billing, monitoring, logging, security, load balancingand clustering, etc.). Thus, as these services may be policy-driven,IaaS users may be able to implement policies to drive load balancing tomaintain application availability and performance.

In some instances, IaaS customers may access resources and servicesthrough a wide area network (WAN), such as the Internet, and can use thecloud provider's services to install the remaining elements of anapplication stack. For example, the user can log in to the IaaS platformto create virtual machines (VMs), install operating systems (OSs) oneach VM, deploy middleware such as databases, create storage buckets forworkloads and backups, and even install enterprise software into thatVM. Customers can then use the provider's services to perform variousfunctions, including balancing network traffic, troubleshootingapplication issues, monitoring performance, managing disaster recovery,etc.

In most cases, a cloud computing model will require the participation ofa cloud provider. The cloud provider may, but need not be, a third-partyservice that specializes in providing (e.g., offering, renting, selling)IaaS. An entity might also opt to deploy a private cloud, becoming itsown provider of infrastructure services.

In some examples, IaaS deployment is the process of putting a newapplication, or a new version of an application, onto a preparedapplication server or the like. It may also include the process ofpreparing the server (e.g., installing libraries, daemons, etc.). Thisis often managed by the cloud provider, below the hypervisor layer(e.g., the servers, storage, network hardware, and virtualization).Thus, the customer may be responsible for handling (OS), middleware,and/or application deployment (e.g., on self-service virtual machines(e.g., that can be spun up on demand) or the like.

In some examples, IaaS provisioning may refer to acquiring computers orvirtual hosts for use, and even installing needed libraries or serviceson them. In most cases, deployment does not include provisioning, andthe provisioning may need to be performed first.

In some cases, there are two different challenges for IaaS provisioning.First, there is the initial challenge of provisioning the initial set ofinfrastructure before anything is running. Second, there is thechallenge of evolving the existing infrastructure (e.g., adding newservices, changing services, removing services, etc.) once everythinghas been provisioned. In some cases, these two challenges may beaddressed by enabling the configuration of the infrastructure to bedefined declaratively. In other words, the infrastructure (e.g., whatcomponents are needed and how they interact) can be defined by one ormore configuration files. Thus, the overall topology of theinfrastructure (e.g., what resources depend on which, and how they eachwork together) can be described declaratively. In some instances, oncethe topology is defined, a workflow can be generated that creates and/ormanages the different components described in the configuration files.

In some examples, an infrastructure may have many interconnectedelements. For example, there may be one or more virtual private clouds(VPCs) (e.g., a potentially on-demand pool of configurable and/or sharedcomputing resources), also known as a core network. In some examples,there may also be one or more security group rules provisioned to definehow the security of the network will be set up and one or more virtualmachines (VMs). Other infrastructure elements may also be provisioned,such as a load balancer, a database, or the like. As more and moreinfrastructure elements are desired and/or added, the infrastructure mayincrementally evolve.

In some instances, continuous deployment techniques may be employed toenable deployment of infrastructure code across various virtualcomputing environments. Additionally, the described techniques canenable infrastructure management within these environments. In someexamples, service teams can write code that is desired to be deployed toone or more, but often many, different production environments (e.g.,across various different geographic locations, sometimes spanning theentire world). However, in some examples, the infrastructure on whichthe code will be deployed must first be set up. In some instances, theprovisioning can be done manually, a provisioning tool may be utilizedto provision the resources, and/or deployment tools may be utilized todeploy the code once the infrastructure is provisioned.

FIG. 17 is a block diagram 1700 illustrating an example pattern of anIaaS architecture, according to at least one embodiment. Serviceoperators 1702 can be communicatively coupled to a secure host tenancy1704 that can include a virtual cloud network (VCN) 1706 and a securehost subnet 1708. In some examples, the service operators 1702 may beusing one or more client computing devices, which may be portablehandheld devices (e.g., an iPhone®, cellular telephone, an iPad®,computing tablet, a personal digital assistant (PDA)) or wearabledevices (e.g., a Google Glass® head-mounted display), running softwaresuch as Microsoft Windows Mobile®, and/or a variety of mobile operatingsystems such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, andthe like, and be Internet, e-mail, short message service (SMS),Blackberry®, or other communication protocol enabled. Alternatively, theclient computing devices can be general purpose personal computersincluding, by way of example, personal computers and/or laptop computersrunning various versions of Microsoft Windows®, Apple Macintosh®, and/orLinux operating systems. The client computing devices can be workstationcomputers running any of a variety of commercially available UNIX® orUNIX-like operating systems, including without limitation the variety ofGNU/Linux operating systems, such as, for example, Google Chrome OS.Alternatively, or in addition, client computing devices may be any otherelectronic device, such as a thin-client computer, an Internet-enabledgaming system (e.g., a Microsoft Xbox gaming console with or without aKinect® gesture input device), and/or a personal messaging device,capable of communicating over a network that can access the VCN 1706and/or the Internet.

The VCN 1706 can include a local peering gateway (LPG) 1710 that can becommunicatively coupled to a secure shell (SSH) VCN 1712 via an LPG 1710contained in the SSH VCN 1712. The SSH VCN 1712 can include an SSHsubnet 1714, and the SSH VCN 1712 can be communicatively coupled to acontrol plane VCN 1716 via the LPG 1710 contained in the control planeVCN 1716. Also, the SSH VCN 1712 can be communicatively coupled to adata plane VCN 1718 via an LPG 1710. The control plane VCN 1716 and thedata plane VCN 1718 can be contained in a service tenancy 1719 that canbe owned and/or operated by the IaaS provider.

The control plane VCN 1716 can include a control plane demilitarizedzone (DMZ) tier 1720 that acts as a perimeter network (e.g., portions ofa corporate network between the corporate intranet and externalnetworks). The DMZ-based servers may have restricted responsibilitiesand help keep security breaches contained. Additionally, the DMZ tier1720 can include one or more load balancer (LB) subnet(s) 1722, acontrol plane app tier 1724 that can include app subnet(s) 1726, acontrol plane data tier 1728 that can include database (DB) subnet(s)1730 (e.g., frontend DB subnet(s) and/or backend DB subnet(s)). The LBsubnet(s) 1722 contained in the control plane DMZ tier 1720 can becommunicatively coupled to the app subnet(s) 1726 contained in thecontrol plane app tier 1724 and an Internet gateway 1734 that can becontained in the control plane VCN 1716, and the app subnet(s) 1726 canbe communicatively coupled to the DB subnet(s) 1730 contained in thecontrol plane data tier 1728 and a service gateway 1736 and a networkaddress translation (NAT) gateway 1738. The control plane VCN 1716 caninclude the service gateway 1736 and the NAT gateway 1738.

The control plane VCN 1716 can include a data plane mirror app tier 1740that can include app subnet(s) 1726. The app subnet(s) 1726 contained inthe data plane mirror app tier 1740 can include a virtual networkinterface controller (VNIC) 1742 that can execute a compute instance1744. The compute instance 1744 can communicatively couple the appsubnet(s) 1726 of the data plane mirror app tier 1740 to app subnet(s)1726 that can be contained in a data plane app tier 1746.

The data plane VCN 1718 can include the data plane app tier 1746, a dataplane DMZ tier 1748, and a data plane data tier 1750. The data plane DMZtier 1748 can include LB subnet(s) 1722 that can be communicativelycoupled to the app subnet(s) 1726 of the data plane app tier 1746 andthe Internet gateway 1734 of the data plane VCN 1718. The app subnet(s)1726 can be communicatively coupled to the service gateway 1736 of thedata plane VCN 1718 and the NAT gateway 1738 of the data plane VCN 1718.The data plane data tier 1750 can also include the DB subnet(s) 1730that can be communicatively coupled to the app subnet(s) 1726 of thedata plane app tier 1746.

The Internet gateway 1734 of the control plane VCN 1716 and of the dataplane VCN 1718 can be communicatively coupled to a metadata managementservice 1752 that can be communicatively coupled to public Internet1754. Public Internet 1754 can be communicatively coupled to the NATgateway 1738 of the control plane VCN 1716 and of the data plane VCN1718. The service gateway 1736 of the control plane VCN 1716 and of thedata plane VCN 1718 can be communicatively coupled to cloud services1756.

In some examples, the service gateway 1736 of the control plane VCN 1716or of the data plane VCN 1718 can make application programming interface(API) calls to cloud services 1756 without going through public Internet1754. The API calls to cloud services 1756 from the service gateway 1736can be one-way: the service gateway 1736 can make API calls to cloudservices 1756, and cloud services 1756 can send requested data to theservice gateway 1736. However, cloud services 1756 may not initiate APIcalls to the service gateway 1736.

In some examples, the secure host tenancy 1704 can be directly connectedto the service tenancy 1719, which may be otherwise isolated. The securehost subnet 1708 can communicate with the SSH subnet 1714 through an LPG1710 that may enable two-way communication over an otherwise isolatedsystem. Connecting the secure host subnet 1708 to the SSH subnet 1714may give the secure host subnet 1708 access to other entities within theservice tenancy 1719.

The control plane VCN 1716 may allow users of the service tenancy 1719to set up or otherwise provision desired resources. Desired resourcesprovisioned in the control plane VCN 1716 may be deployed or otherwiseused in the data plane VCN 1718. In some examples, the control plane VCN1716 can be isolated from the data plane VCN 1718, and the data planemirror app tier 1740 of the control plane VCN 1716 can communicate withthe data plane app tier 1746 of the data plane VCN 1718 via VNICs 1742that can be contained in the data plane mirror app tier 1740 and thedata plane app tier 1746.

In some examples, users of the system, or customers, can make requests,for example create, read, update, or delete (CRUD) operations, throughpublic Internet 1754 that can communicate the requests to the metadatamanagement service 1752. The metadata management service 1752 cancommunicate the request to the control plane VCN 1716 through theInternet gateway 1734. The request can be received by the LB subnet(s)1722 contained in the control plane DMZ tier 1720. The LB subnet(s) 1722may determine that the request is valid, and in response to thisdetermination, the LB subnet(s) 1722 can transmit the request to appsubnet(s) 1726 contained in the control plane app tier 1724. If therequest is validated and requires a call to public Internet 1754, thecall to public Internet 1754 may be transmitted to the NAT gateway 1738that can make the call to public Internet 1754. Memory that may bedesired to be stored by the request can be stored in the DB subnet(s)1730.

In some examples, the data plane mirror app tier 1740 can facilitatedirect communication between the control plane VCN 1716 and the dataplane VCN 1718. For example, changes, updates, or other suitablemodifications to configuration may be desired to be applied to theresources contained in the data plane VCN 1718. Via a VNIC 1742, thecontrol plane VCN 1716 can directly communicate with, and can therebyexecute the changes, updates, or other suitable modifications toconfiguration to, resources contained in the data plane VCN 1718.

In some embodiments, the control plane VCN 1716 and the data plane VCN1718 can be contained in the service tenancy 1719. In this case, theuser, or the customer, of the system may not own or operate either thecontrol plane VCN 1716 or the data plane VCN 1718. Instead, the IaaSprovider may own or operate the control plane VCN 1716 and the dataplane VCN 1718, both of which may be contained in the service tenancy1719. This embodiment can enable isolation of networks that may preventusers or customers from interacting with other users', or othercustomers', resources. Also, this embodiment may allow users orcustomers of the system to store databases privately without needing torely on public Internet 1754, which may not have a desired level ofsecurity, for storage.

In other embodiments, the LB subnet(s) 1722 contained in the controlplane VCN 1716 can be configured to receive a signal from the servicegateway 1736. In this embodiment, the control plane VCN 1716 and thedata plane VCN 1718 may be configured to be called by a customer of theIaaS provider without calling public Internet 1754. Customers of theIaaS provider may desire this embodiment since database(s) that thecustomers use may be controlled by the IaaS provider and may be storedon the service tenancy 1719, which may be isolated from public Internet1754.

FIG. 18 is a block diagram 1800 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1802 (e.g., service operators 1702 of FIG. 17 ) can becommunicatively coupled to a secure host tenancy 1804 (e.g., the securehost tenancy 1704 of FIG. 17 ) that can include a virtual cloud network(VCN) 1806 (e.g., the VCN 1706 of FIG. 17 ) and a secure host subnet1808 (e.g., the secure host subnet 1708 of FIG. 17 ). The VCN 1806 caninclude a local peering gateway (LPG) 1810 (e.g., the LPG 1710 of FIG.17 ) that can be communicatively coupled to a secure shell (SSH) VCN1812 (e.g., the SSH VCN 1712 of FIG. 17 ) via an LPG 1710 contained inthe SSH VCN 1812. The SSH VCN 1812 can include an SSH subnet 1814 (e.g.,the SSH subnet 1714 of FIG. 17 ), and the SSH VCN 1812 can becommunicatively coupled to a control plane VCN 1816 (e.g., the controlplane VCN 1716 of FIG. 17 ) via an LPG 1810 contained in the controlplane VCN 1816. The control plane VCN 1816 can be contained in a servicetenancy 1819 (e.g., the service tenancy 1719 of FIG. 17), and the dataplane VCN 1818 (e.g., the data plane VCN 1718 of FIG. 17 ) can becontained in a customer tenancy 1821 that may be owned or operated byusers, or customers, of the system.

The control plane VCN 1816 can include a control plane DMZ tier 1820(e.g., the control plane DMZ tier 1720 of FIG. 17 ) that can include LBsubnet(s) 1822 (e.g., LB subnet(s) 1722 of FIG. 17 ), a control planeapp tier 1824 (e.g., the control plane app tier 1724 of FIG. 17 ) thatcan include app subnet(s) 1826 (e.g., app subnet(s) 1726 of FIG. 17 ), acontrol plane data tier 1828 (e.g., the control plane data tier 1728 ofFIG. 17 ) that can include database (DB) subnet(s) 1830 (e.g., similarto DB subnet(s) 1730 of FIG. 17 ). The LB subnet(s) 1822 contained inthe control plane DMZ tier 1820 can be communicatively coupled to theapp subnet(s) 1826 contained in the control plane app tier 1824 and anInternet gateway 1834 (e.g., the Internet gateway 1734 of FIG. 17 ) thatcan be contained in the control plane VCN 1816, and the app subnet(s)1826 can be communicatively coupled to the DB subnet(s) 1830 containedin the control plane data tier 1828 and a service gateway 1836 (e.g.,the service gateway of FIG. 17 ) and a network address translation (NAT)gateway 1838 (e.g., the NAT gateway 1738 of FIG. 17 ). The control planeVCN 1816 can include the service gateway 1836 and the NAT gateway 1838.

The control plane VCN 1816 can include a data plane mirror app tier 1840(e.g., the data plane mirror app tier 1740 of FIG. 17 ) that can includeapp subnet(s) 1826. The app subnet(s) 1826 contained in the data planemirror app tier 1840 can include a virtual network interface controller(VNIC) 1842 (e.g., the VNIC of 1742) that can execute a compute instance1844 (e.g., similar to the compute instance 1744 of FIG. 17 ). Thecompute instance 1844 can facilitate communication between the appsubnet(s) 1826 of the data plane mirror app tier 1840 and the appsubnet(s) 1826 that can be contained in a data plane app tier 1846(e.g., the data plane app tier 1746 of FIG. 17 ) via the VNIC 1842contained in the data plane mirror app tier 1840 and the VNIC 1842contained in the data plane app tier 1846.

The Internet gateway 1834 contained in the control plane VCN 1816 can becommunicatively coupled to a metadata management service 1852 (e.g., themetadata management service 1752 of FIG. 17 ) that can becommunicatively coupled to public Internet 1854 (e.g., public Internet1754 of FIG. 17 ). Public Internet 1854 can be communicatively coupledto the NAT gateway 1838 contained in the control plane VCN 1816. Theservice gateway 1836 contained in the control plane VCN 1816 can becommunicatively coupled to cloud services 1856 (e.g., cloud services1756 of FIG. 17 ).

In some examples, the data plane VCN 1818 can be contained in thecustomer tenancy 1821. In this case, the IaaS provider may provide thecontrol plane VCN 1816 for each customer, and the IaaS provider may, foreach customer, set up a unique compute instance 1844 that is containedin the service tenancy 1819. Each compute instance 1844 may allowcommunication between the control plane VCN 1816, contained in theservice tenancy 1819, and the data plane VCN 1818 that is contained inthe customer tenancy 1821. The compute instance 1844 may allow resourcesthat are provisioned in the control plane VCN 1816 that is contained inthe service tenancy 1819, to be deployed or otherwise used in the dataplane VCN 1818 that is contained in the customer tenancy 1821.

In other examples, the customer of the IaaS provider may have databasesthat live in the customer tenancy 1821. In this example, the controlplane VCN 1816 can include the data plane mirror app tier 1840 that caninclude app subnet(s) 1826. The data plane mirror app tier 1840 canreside in the data plane VCN 1818, but the data plane mirror app tier1840 may not live in the data plane VCN 1818. That is, the data planemirror app tier 1840 may have access to the customer tenancy 1821, butthe data plane mirror app tier 1840 may not exist in the data plane VCN1818 or be owned or operated by the customer of the IaaS provider. Thedata plane mirror app tier 1840 may be configured to make calls to thedata plane VCN 1818 but may not be configured to make calls to anyentity contained in the control plane VCN 1816. The customer may desireto deploy or otherwise use resources in the data plane VCN 1818 that areprovisioned in the control plane VCN 1816, and the data plane mirror apptier 1840 can facilitate the desired deployment, or other usage ofresources, of the customer.

In some embodiments, the customer of the IaaS provider can apply filtersto the data plane VCN 1818. In this embodiment, the customer candetermine what the data plane VCN 1818 can access, and the customer mayrestrict access to public Internet 1854 from the data plane VCN 1818.The IaaS provider may not be able to apply filters or otherwise controlaccess of the data plane VCN 1818 to any outside networks or databases.Applying filters and controls by the customer onto the data plane VCN1818, contained in the customer tenancy 1821, can help isolate the dataplane VCN 1818 from other customers and from public Internet 1854.

In some embodiments, cloud services 1856 can be called by the servicegateway 1836 to access services that may not exist on public Internet1854, on the control plane VCN 1816, or on the data plane VCN 1818. Theconnection between cloud services 1856 and the control plane VCN 1816 orthe data plane VCN 1818 may not be live or continuous. Cloud services1856 may exist on a different network owned or operated by the IaaSprovider. Cloud services 1856 may be configured to receive calls fromthe service gateway 1836 and may be configured to not receive calls frompublic Internet 1854. Some cloud services 1856 may be isolated fromother cloud services 1856, and the control plane VCN 1816 may beisolated from cloud services 1856 that may not be in the same region asthe control plane VCN 1816. For example, the control plane VCN 1816 maybe located in “Region 1,” and cloud service “Deployment 17” may belocated in Region 1 and in “Region 2.” If a call to Deployment 17 ismade by the service gateway 1836 contained in the control plane VCN 1816located in Region 1, the call may be transmitted to Deployment 17 inRegion 1. In this example, the control plane VCN 1816, or Deployment 17in Region 1, may not be communicatively coupled to, or otherwise incommunication with, Deployment 17 in Region 2.

FIG. 19 is a block diagram 1900 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 1902 (e.g., service operators 1702 of FIG. 17 ) can becommunicatively coupled to a secure host tenancy 1904 (e.g., the securehost tenancy 1704 of FIG. 17 ) that can include a virtual cloud network(VCN) 1906 (e.g., the VCN 1706 of FIG. 17 ) and a secure host subnet1908 (e.g., the secure host subnet 1708 of FIG. 17 ). The VCN 1906 caninclude an LPG 1910 (e.g., the LPG 1710 of FIG. 17 ) that can becommunicatively coupled to an SSH VCN 1912 (e.g., the SSH VCN 1712 ofFIG. 17 ) via an LPG 1910 contained in the SSH VCN 1912. The SSH VCN1912 can include an SSH subnet 1914 (e.g., the SSH subnet 1714 of FIG.17 ), and the SSH VCN 1912 can be communicatively coupled to a controlplane VCN 1916 (e.g., the control plane VCN 1716 of FIG. 17 ) via an LPG1910 contained in the control plane VCN 1916 and to a data plane VCN1918 (e.g., the data plane 1718 of FIG. 17 ) via an LPG 1910 containedin the data plane VCN 1918. The control plane VCN 1916 and the dataplane VCN 1918 can be contained in a service tenancy 1919 (e.g., theservice tenancy 1719 of FIG. 17 ).

The control plane VCN 1916 can include a control plane DMZ tier 1920(e.g., the control plane DMZ tier 1720 of FIG. 17 ) that can includeload balancer (LB) subnet(s) 1922 (e.g., LB subnet(s) 1722 of FIG. 17 ),a control plane app tier 1924 (e.g., the control plane app tier 1724 ofFIG. 17 ) that can include app subnet(s) 1926 (e.g., similar to appsubnet(s) 1726 of FIG. 17 ), and a control plane data tier 1928 (e.g.,the control plane data tier 1728 of FIG. 17 ) that can include DBsubnet(s) 1930. The LB subnet(s) 1922 contained in the control plane DMZtier 1920 can be communicatively coupled to the app subnet(s) 1926contained in the control plane app tier 1924 and to an Internet gateway1934 (e.g., the Internet gateway 1734 of FIG. 17 ) that can be containedin the control plane VCN 1916, and the app subnet(s) 1926 can becommunicatively coupled to the DB subnet(s) 1930 contained in thecontrol plane data tier 1928 and to a service gateway 1936 (e.g., theservice gateway of FIG. 17 ) and a network address translation (NAT)gateway 1938 (e.g., the NAT gateway 1738 of FIG. 17 ). The control planeVCN 1916 can include the service gateway 1936 and the NAT gateway 1938.

The data plane VCN 1918 can include a data plane app tier 1946 (e.g.,the data plane app tier 1746 of FIG. 17 ), a data plane DMZ tier 1948(e.g., the data plane DMZ tier 1748 of FIG. 17 ), and a data plane datatier 1950 (e.g., the data plane data tier 1750 of FIG. 17 ). The dataplane DMZ tier 1948 can include LB subnet(s) 1922 that can becommunicatively coupled to trusted app subnet(s) 1960 and untrusted appsubnet(s) 1962 of the data plane app tier 1946 and the Internet gateway1934 contained in the data plane VCN 1918. The trusted app subnet(s)1960 can be communicatively coupled to the service gateway 1936contained in the data plane VCN 1918, the NAT gateway 1938 contained inthe data plane VCN 1918, and DB subnet(s) 1930 contained in the dataplane data tier 1950. The untrusted app subnet(s) 1962 can becommunicatively coupled to the service gateway 1936 contained in thedata plane VCN 1918 and DB subnet(s) 1930 contained in the data planedata tier 1950. The data plane data tier 1950 can include DB subnet(s)1930 that can be communicatively coupled to the service gateway 1936contained in the data plane VCN 1918.

The untrusted app subnet(s) 1962 can include one or more primary VNICs1964(1)-(N) that can be communicatively coupled to tenant virtualmachines (VMs) 1966(1)-(N). Each tenant VM 1966(1)-(N) can becommunicatively coupled to a respective app subnet 1967(1)-(N) that canbe contained in respective container egress VCNs 1968(1)-(N) that can becontained in respective customer tenancies 1970(1)-(N). Respectivesecondary VNICs 1972(1)-(N) can facilitate communication between theuntrusted app subnet(s) 1962 contained in the data plane VCN 1918 andthe app subnet contained in the container egress VCNs 1968(1)-(N). Eachcontainer egress VCNs 1968(1)-(N) can include a NAT gateway 1938 thatcan be communicatively coupled to public Internet 1954 (e.g., publicInternet 1754 of FIG. 17 ).

The Internet gateway 1934 contained in the control plane VCN 1916 andcontained in the data plane VCN 1918 can be communicatively coupled to ametadata management service 1952 (e.g., the metadata management system1752 of FIG. 17 ) that can be communicatively coupled to public Internet1954. Public Internet 1954 can be communicatively coupled to the NATgateway 1938 contained in the control plane VCN 1916 and contained inthe data plane VCN 1918. The service gateway 1936 contained in thecontrol plane VCN 1916 and contained in the data plane VCN 1918 can becommunicatively coupled to cloud services 1956.

In some embodiments, the data plane VCN 1918 can be integrated withcustomer tenancies 1970. This integration can be useful or desirable forcustomers of the IaaS provider in some cases such as a case in whichsupport may be desired when executing code. The customer may providecode to run that may be destructive, may communicate with other customerresources, or may otherwise cause undesirable effects. In response tothis, the IaaS provider may determine whether to run code given to theIaaS provider by the customer.

In some examples, the customer of the IaaS provider may grant temporarynetwork access to the IaaS provider and request a function to beattached to the data plane tier app 1946. Code to run the function maybe executed in the VMs 1966(1)-(N), and the code may not be configuredto run anywhere else on the data plane VCN 1918. Each VM 1966(1)-(N) maybe connected to one customer tenancy 1970. Respective containers1971(1)-(N) contained in the VMs 1966(1)-(N) may be configured to runthe code. In this case, there can be a dual isolation (e.g., thecontainers 1971(1)-(N) running code, where the containers 1971(1)-(N)may be contained in at least the VMs 1966(1)-(N) that are contained inthe untrusted app subnet(s) 1962), which may help prevent incorrect orotherwise undesirable code from damaging the network of the IaaSprovider or from damaging a network of a different customer. Thecontainers 1971(1)-(N) may be communicatively coupled to the customertenancy 1970 and may be configured to transmit or receive data from thecustomer tenancy 1970. The containers 1971(1)-(N) may not be configuredto transmit or receive data from any other entity in the data plane VCN1918. Upon completion of running the code, the IaaS provider may kill orotherwise dispose of the containers 1971(1)-(N).

In some embodiments, the trusted app subnet(s) 1960 may run code thatmay be owned or operated by the IaaS provider. In this embodiment, thetrusted app subnet(s) 1960 may be communicatively coupled to the DBsubnet(s) 1930 and be configured to execute CRUD operations in the DBsubnet(s) 1930. The untrusted app subnet(s) 1962 may be communicativelycoupled to the DB subnet(s) 1930, but in this embodiment, the untrustedapp subnet(s) may be configured to execute read operations in the DBsubnet(s) 1930. The containers 1971(1)-(N) that can be contained in theVM 1966(1)-(N) of each customer and that may run code from the customermay not be communicatively coupled with the DB subnet(s) 1930.

In other embodiments, the control plane VCN 1916 and the data plane VCN1918 may not be directly communicatively coupled. In this embodiment,there may be no direct communication between the control plane VCN 1916and the data plane VCN 1918. However, communication can occur indirectlythrough at least one method. An LPG 1910 may be established by the IaaSprovider that can facilitate communication between the control plane VCN1916 and the data plane VCN 1918. In another example, the control planeVCN 1916 or the data plane VCN 1918 can make a call to cloud services1956 via the service gateway 1936. For example, a call to cloud services1956 from the control plane VCN 1916 can include a request for a servicethat can communicate with the data plane VCN 1918.

FIG. 20 is a block diagram 2000 illustrating another example pattern ofan IaaS architecture, according to at least one embodiment. Serviceoperators 2002 (e.g., service operators 1702 of FIG. 17 ) can becommunicatively coupled to a secure host tenancy 2004 (e.g., the securehost tenancy 1704 of FIG. 17 ) that can include a virtual cloud network(VCN) 2006 (e.g., the VCN 1706 of FIG. 17 ) and a secure host subnet2008 (e.g., the secure host subnet 1708 of FIG. 17 ). The VCN 2006 caninclude an LPG 2010 (e.g., the LPG 1710 of FIG. 17 ) that can becommunicatively coupled to an SSH VCN 2012 (e.g., the SSH VCN 1712 ofFIG. 17 ) via an LPG 2010 contained in the SSH VCN 2012. The SSH VCN2012 can include an SSH subnet 2014 (e.g., the SSH subnet 1714 of FIG.17 ), and the SSH VCN 2012 can be communicatively coupled to a controlplane VCN 2016 (e.g., the control plane VCN 1716 of FIG. 17 ) via an LPG2010 contained in the control plane VCN 2016 and to a data plane VCN2018 (e.g., the data plane 1718 of FIG. 17 ) via an LPG 2010 containedin the data plane VCN 2018. The control plane VCN 2016 and the dataplane VCN 2018 can be contained in a service tenancy 2019 (e.g., theservice tenancy 1719 of FIG. 17 ).

The control plane VCN 2016 can include a control plane DMZ tier 2020(e.g., the control plane DMZ tier 1720 of FIG. 17 ) that can include LBsubnet(s) 2022 (e.g., LB subnet(s) 1722 of FIG. 17 ), a control planeapp tier 2024 (e.g., the control plane app tier 1724 of FIG. 17 ) thatcan include app subnet(s) 2026 (e.g., app subnet(s) 1726 of FIG. 17 ), acontrol plane data tier 2028 (e.g., the control plane data tier 1728 ofFIG. 17 ) that can include DB subnet(s) 2030 (e.g., DB subnet(s) 1930 ofFIG. 19 ). The LB subnet(s) 2022 contained in the control plane DMZ tier2020 can be communicatively coupled to the app subnet(s) 2026 containedin the control plane app tier 2024 and to an Internet gateway 2034(e.g., the Internet gateway 1734 of FIG. 17 ) that can be contained inthe control plane VCN 2016, and the app subnet(s) 2026 can becommunicatively coupled to the DB subnet(s) 2030 contained in thecontrol plane data tier 2028 and to a service gateway 2036 (e.g., theservice gateway of FIG. 17 ) and a network address translation (NAT)gateway 2038 (e.g., the NAT gateway 1738 of FIG. 17 ). The control planeVCN 2016 can include the service gateway 2036 and the NAT gateway 2038.

The data plane VCN 2018 can include a data plane app tier 2046 (e.g.,the data plane app tier 1746 of FIG. 17 ), a data plane DMZ tier 2048(e.g., the data plane DMZ tier 1748 of FIG. 17 ), and a data plane datatier 2050 (e.g., the data plane data tier 1750 of FIG. 17 ). The dataplane DMZ tier 2048 can include LB subnet(s) 2022 that can becommunicatively coupled to trusted app subnet(s) 2060 (e.g., trusted appsubnet(s) 1960 of FIG. 19 ) and untrusted app subnet(s) 2062 (e.g.,untrusted app subnet(s) 1962 of FIG. 19 ) of the data plane app tier2046 and the Internet gateway 2034 contained in the data plane VCN 2018.The trusted app subnet(s) 2060 can be communicatively coupled to theservice gateway 2036 contained in the data plane VCN 2018, the NATgateway 2038 contained in the data plane VCN 2018, and DB subnet(s) 2030contained in the data plane data tier 2050. The untrusted app subnet(s)2062 can be communicatively coupled to the service gateway 2036contained in the data plane VCN 2018 and DB subnet(s) 2030 contained inthe data plane data tier 2050. The data plane data tier 2050 can includeDB subnet(s) 2030 that can be communicatively coupled to the servicegateway 2036 contained in the data plane VCN 2018.

The untrusted app subnet(s) 2062 can include primary VNICs 2064(1)-(N)that can be communicatively coupled to tenant virtual machines (VMs)2066(1)-(N) residing within the untrusted app subnet(s) 2062. Eachtenant VM 2066(1)-(N) can run code in a respective container2067(1)-(N), and be communicatively coupled to an app subnet 2026 thatcan be contained in a data plane app tier 2046 that can be contained ina container egress VCN 2068. Respective secondary VNICs 2072(1)-(N) canfacilitate communication between the untrusted app subnet(s) 2062contained in the data plane VCN 2018 and the app subnet contained in thecontainer egress VCN 2068. The container egress VCN can include a NATgateway 2038 that can be communicatively coupled to public Internet 2054(e.g., public Internet 1754 of FIG. 17 ).

The Internet gateway 2034 contained in the control plane VCN 2016 andcontained in the data plane VCN 2018 can be communicatively coupled to ametadata management service 2052 (e.g., the metadata management system1752 of FIG. 17 ) that can be communicatively coupled to public Internet2054. Public Internet 2054 can be communicatively coupled to the NATgateway 2038 contained in the control plane VCN 2016 and contained inthe data plane VCN 2018. The service gateway 2036 contained in thecontrol plane VCN 2016 and contained in the data plane VCN 2018 can becommunicatively coupled to cloud services 2056.

In some examples, the pattern illustrated by the architecture of blockdiagram 2000 of FIG. 20 may be considered an exception to the patternillustrated by the architecture of block diagram 1900 of FIG. 19 and maybe desirable for a customer of the IaaS provider if the IaaS providercannot directly communicate with the customer (e.g., a disconnectedregion). The respective containers 2067(1)-(N) that are contained in theVMs 2066(1)-(N) for each customer can be accessed in real-time by thecustomer. The containers 2067(1)-(N) may be configured to make calls torespective secondary VNICs 2072(1)-(N) contained in app subnet(s) 2026of the data plane app tier 2046 that can be contained in the containeregress VCN 2068. The secondary VNICs 2072(1)-(N) can transmit the callsto the NAT gateway 2038 that may transmit the calls to public Internet2054. In this example, the containers 2067(1)-(N) that can be accessedin real-time by the customer can be isolated from the control plane VCN2016 and can be isolated from other entities contained in the data planeVCN 2018. The containers 2067(1)-(N) may also be isolated from resourcesfrom other customers.

In other examples, the customer can use the containers 2067(1)-(N) tocall cloud services 2056. In this example, the customer may run code inthe containers 2067(1)-(N) that requests a service from cloud services2056. The containers 2067(1)-(N) can transmit this request to thesecondary VNICs 2072(1)-(N) that can transmit the request to the NATgateway that can transmit the request to public Internet 2054. PublicInternet 2054 can transmit the request to LB subnet(s) 2022 contained inthe control plane VCN 2016 via the Internet gateway 2034. In response todetermining the request is valid, the LB subnet(s) can transmit therequest to app subnet(s) 2026 that can transmit the request to cloudservices 2056 via the service gateway 2036.

It should be appreciated that IaaS architectures 1700, 1800, 1900, 2000depicted in the figures may have other components than those depicted.Further, the embodiments shown in the figures are only some examples ofa cloud infrastructure system that may incorporate an embodiment of thedisclosure. In some other embodiments, the IaaS systems may have more orfewer components than shown in the figures, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

In certain embodiments, the IaaS systems described herein may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such an IaaS system is the Oracle Cloud Infrastructure (OCI)provided by the present assignee.

FIG. 21 illustrates an example computer system 2100, in which variousembodiments may be implemented. The system 2100 may be used to implementany of the computer systems described above. As shown in the figure,computer system 2100 includes a processing unit 2104 that communicateswith a number of peripheral subsystems via a bus subsystem 2102. Theseperipheral subsystems may include a processing acceleration unit 2106,an I/O subsystem 2108, a storage subsystem 2118 and a communicationssubsystem 2124. Storage subsystem 2118 includes tangiblecomputer-readable storage media 2122 and a system memory 2110.

Bus subsystem 2102 provides a mechanism for letting the variouscomponents and subsystems of computer system 2100 communicate with eachother as intended. Although bus subsystem 2102 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 2102 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 2104, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 2100. One or more processorsmay be included in processing unit 2104. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 2104 may be implemented as one or more independent processing units2132 and/or 2134 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 2104 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 2104 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)2104 and/or in storage subsystem 2118. Through suitable programming,processor(s) 2104 can provide various functionalities described above.Computer system 2100 may additionally include a processing accelerationunit 2106, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 2108 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, or medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system2100 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 2100 may comprise a storage subsystem 2118 thatcomprises software elements, shown as being currently located within asystem memory 2110. System memory 2110 may store program instructionsthat are loadable and executable on processing unit 2104, as well asdata generated during the execution of these programs.

Depending on the configuration and type of computer system 2100, systemmemory 2110 may be volatile (such as random access memory (RAM)) and/ornon-volatile (such as read-only memory (ROM), flash memory, etc.). TheRAM typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated and executed by processingunit 2104. In some implementations, system memory 2110 may includemultiple different types of memory, such as static random access memory(SRAM) or dynamic random access memory (DRAM). In some implementations,a basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements within computer system2100, such as during start-up, may typically be stored in the ROM. Byway of example, and not limitation, system memory 2110 also illustratesapplication programs 2112, which may include client applications, Webbrowsers, mid-tier applications, relational database management systems(RDBMS), etc., program data 2114, and an operating system 2116. By wayof example, operating system 2116 may include various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems, avariety of commercially available UNIX® or UNIX-like operating systems(including without limitation the variety of GNU/Linux operatingsystems, the Google Chrome® OS, and the like) and/or mobile operatingsystems such as iOS, Windows® Phone, Android® OS, BlackBerry® 21 OS, andPalm® OS operating systems.

Storage subsystem 2118 may also provide a tangible computer-readablestorage medium for storing the basic programming and data constructsthat provide the functionality of some embodiments. Software (programs,code modules, instructions) that, when executed by a processor, providesthe functionality described above may be stored in storage subsystem2118. These software modules or instructions may be executed byprocessing unit 2104. Storage subsystem 2118 may also provide arepository for storing data used in accordance with the presentdisclosure.

Storage subsystem 2100 may also include a computer-readable storagemedia reader 2120 that can further be connected to computer-readablestorage media 2122. Together and, optionally, in combination with systemmemory 2110, computer-readable storage media 2122 may comprehensivelyrepresent remote, local, fixed, and/or removable storage devices plusstorage media for temporarily and/or more permanently containing,storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 2122 containing code, or portions ofcode, can also include any appropriate media known or used in the art,including storage media and communication media, such as, but notlimited to, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computing system 2100.

By way of example, computer-readable storage media 2122 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 2122 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 2122 may also includesolid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 2100.

Communications subsystem 2124 provides an interface to other computersystems and networks. Communications subsystem 2124 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 2100. For example, communications subsystem 2124may enable computer system 2100 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 2124 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 2124 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 2124 may also receiveinput communication in the form of structured and/or unstructured datafeeds 2126, event streams 2128, event updates 2130, and the like onbehalf of one or more users who may use computer system 2100.

By way of example, communications subsystem 2124 may be configured toreceive data feeds 2126 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 2124 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 2128 of real-time events and/or event updates 2130, thatmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g., network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like.

Communications subsystem 2124 may also be configured to output thestructured and/or unstructured data feeds 2126, event streams 2128,event updates 2130, and the like to one or more databases that may be incommunication with one or more streaming data source computers coupledto computer system 2100.

Computer system 2100 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head-mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

In the foregoing description, for the purposes of explanation, specificdetails are set forth to provide a thorough understanding of examples ofthe disclosure. However, it will be apparent that various examples maybe practiced without these specific details. The ensuing descriptionprovides examples only and is not intended to limit the scope,applicability, or configuration of the disclosure. Rather, the ensuingdescription of the examples will provide those skilled in the art withan enabling description for implementing an example. It should beunderstood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope ofthe disclosure as set forth in the appended claims. The figures anddescription are not intended to be restrictive. Circuits, systems,networks, processes, and other components may be shown as components inblock diagram form in order not to obscure the examples in unnecessarydetail. In other instances, well-known circuits, processes, algorithms,structures, and techniques may be shown without unnecessary detail inorder to avoid obscuring the examples. The teachings disclosed hereincan also be applied to various types of applications such as mobileapplications, non-mobile applications, desktop applications, webapplications, enterprise applications, and the like. Further, theteachings of this disclosure are not restricted to a particularoperating environment (e.g., operating systems, devices, platforms, andthe like), but instead can be applied to multiple different operatingenvironments.

Also, it is noted that individual examples may be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations may beperformed in parallel or concurrently. In addition, the order of theoperations may be rearranged. A process is terminated when itsoperations are completed, but the process could have additional stepsnot included in a figure. A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, and so on. When aprocess corresponds to a function, its termination may correspond to areturn of the function to the calling function or the main function.

The words “example” and “exemplary” are used herein to mean “serving asan example, instance, or illustration.” Any embodiment or designdescribed herein as “exemplary” or “example” is not necessarily to beconstrued as preferred or advantageous over other embodiments ordesigns.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable storage medium or computer-readable storage mediummay include a non-transitory medium in which data may be stored andwhich does not include carrier waves and/or transitory electronicsignals propagating wirelessly or over wired connections. Examples of anon-transitory medium may include, but are not limited to, a magneticdisk or tape, optical storage media such as compact disk (CD) or digitalversatile disk (DVD), flash memory, or memory or memory devices. Acomputer-program product may include code and/or machine-executableinstructions that may represent a procedure, a function, a subprogram, aprogram, a routine, a subroutine, a module, a software package, a class,or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or ahardware circuit by passing and/or receiving information, data,arguments, parameters, or memory contents. Information, arguments,parameters, data, and so forth may be passed, forwarded, or transmittedvia any suitable means including memory sharing, message passing, tokenpassing, network transmission, and so forth.

Furthermore, examples may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middleware,or microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.Systems depicted in some of the figures may be provided in variousconfigurations. In some examples, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.Where components are described as being “configured to” perform certainoperations, such configuration may be accomplished, for example, bydesigning electronic circuits or other hardware to perform theoperation, by programming or controlling electronic circuits (e.g.,microprocessors or other suitable electronic circuits) to perform theoperation, or any combination thereof.

Although specific embodiments of the disclosure have been described,various modifications, alterations, alternative constructions, andequivalents are also encompassed within the scope of the disclosure.Embodiments of the present disclosure are not restricted to operationwithin certain specific data processing environments, but are free tooperate within a plurality of data processing environments.Additionally, although embodiments of the present disclosure have beendescribed using a particular series of transactions and steps, it shouldbe apparent to those skilled in the art that the scope of the presentdisclosure is not limited to the described series of transactions andsteps. Various features and aspects of the above-described embodimentsmay be used individually or jointly.

Further, while embodiments of the present disclosure have been describedusing a particular combination of hardware and software, it should berecognized that other combinations of hardware and software are alsowithin the scope of the present disclosure. Embodiments of the presentdisclosure may be implemented only in hardware, or only in software, orusing combinations thereof. The various processes described herein canbe implemented on the same processor or different processors in anycombination. Accordingly, where components or modules are described asbeing configured to perform certain operations, such configuration canbe accomplished, e.g., by designing electronic circuits to perform theoperation, by programming programmable electronic circuits (such asmicroprocessors) to perform the operation, or any combination thereof.Processes can communicate using a variety of techniques including, butnot limited to, conventional techniques for inter-process communication,and different pairs of processes may use different techniques, or thesame pair of processes may use different techniques at different times.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that additions, subtractions, deletions, and other modificationsand changes may be made thereunto without departing from the broaderspirit and scope as set forth in the claims. Thus, although specificdisclosure embodiments have been described, these are not intended to belimiting. Various modifications and equivalents are within the scope ofthe following claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected” is to be construed as partly or wholly contained within,attached to, or joined together, even if there is something intervening.Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate embodiments of the disclosure anddoes not pose a limitation on the scope of the disclosure unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe disclosure.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is intended to be understoodwithin the context as used in general to present that an item, term,etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y,and/or Z). Thus, such disjunctive language is not generally intended to,and should not, imply that certain embodiments require at least one ofX, at least one of Y, or at least one of Z to each be present.

Preferred embodiments of this disclosure are described herein, includingthe best mode known for carrying out the disclosure. Variations of thosepreferred embodiments may become apparent to those of ordinary skill inthe art upon reading the foregoing description. Those of ordinary skillshould be able to employ such variations as appropriate and thedisclosure may be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

In the foregoing specification, aspects of the disclosure are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the disclosure is not limited thereto. Variousfeatures and aspects of the above-described disclosure may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A computer system comprising: a virtual networkof a customer, wherein the virtual network is hosted on a substratenetwork and comprises a compute instance; a first network virtualizationdevice of the substrate network, wherein the first networkvirtualization device comprises one or more processors and one or morememories storing computer-readable instructions that, upon execution bythe one or more processors, configure the first network virtualizationdevice to: receive a packet generated by the compute instance;determine, based on a flow packet rule associated with the computeinstance, a network boundary defining a set of one or more networks suchthat a first packet having a destination within the network boundary canflow and such that a second packet having a destination outside of thenetwork boundary is to be dropped; determine that a flow of the packetis within the network boundary; generate data indicating that the flowof the packet is permitted within the network boundary; include the datain the packet; and send, to a second network virtualization device andbased on the flow, the packet that includes the data.
 2. The computersystem of claim 1, wherein the network boundary is defined based oninput of the customer and corresponds to at least one of: a layer 2 (L2)virtual local area network (VLAN) within the virtual network, a layer 3(L3) subnet within the virtual network, the virtual network, a privatenetwork of the customer peered with the virtual network, another virtualnetwork peered with the virtual network, or a public network.
 3. Thecomputer system of claim 1, wherein the compute instance executes on ahost machine of the substrate network, wherein the first networkvirtualization device receives the packet from the host machine,executes a virtual network interface card that is associated with thecompute instance and that is usable to send the packet on the virtualnetwork, and stores the packet flow rule in association with the virtualnetwork interface card.
 4. The computer system of claim 1, wherein theexecution of the computer-readable instructions further configures thefirst network virtualization device to: receive customer data indicatingthe packet flow rule, the customer data corresponding to a selection bythe customer of the network boundary from a set of network boundaries;and generate the packet flow rule based on the customer data.
 5. Thecomputer system of claim 4, wherein the customer data further indicatesthat the network boundary is selected specifically for the computeinstance, and wherein the packet flow rule is generated specifically forthe compute instance.
 6. The computer system of claim 4, wherein thecustomer data further indicates that the network boundary is selectedfor a plurality of compute instances that are hosted on the virtualnetwork of the customer and that comprise a second compute instance, andwherein a second packet flow rule is associated with the second computeinstance and indicates the network boundary.
 7. The computer system ofclaim 1, wherein the data is included in a field of a header of thepacket, wherein the field indicates the network boundary.
 8. Thecomputer system of claim 7, wherein the field further indicates thatpackets generated by the compute instance are prohibited from flowingwithin another customer-selectable network boundary.
 9. The computersystem of claim 1, wherein the second network virtualization devicecomprises one or more second processors and one or more second memoriesstoring second computer-readable instructions that, upon execution bythe one or more second processors, configure the second networkvirtualization device to: receive the packet sent by the first networkvirtualization device; and enforce the network boundary by at leastdetermining, based on the data included in the packet, that the packetis permitted to flow within the network boundary, and sending the packetto a third network virtualization device or a host machine within thenetwork boundary, wherein the host machine executes a second computeinstance that is a destination of the packet.
 10. The computer system ofclaim 1, wherein the second network virtualization device comprises oneor more second processors and one or more second memories storing secondcomputer-readable instructions that, upon execution by the one or moresecond processors, configure the second network virtualization deviceto: receive a third packet generated by a second compute instance; andenforce a second network boundary by at least determining, based onsecond data included in the third packet, that the third packet ispermitted to flow within the second network boundary, wherein the seconddata is included in the third packet based on a third packet flow ruleassociated with the second compute instance, and wherein the secondnetwork boundary is the same as or different from the network boundary,determining that the first network virtualization device is within thesecond network boundary, and sending the third packet to the firstnetwork virtualization device.
 11. The computer system of claim 1,wherein the second network virtualization device comprises one or moresecond processors and one or more second memories storing secondcomputer-readable instructions that, upon execution by the one or moresecond processors, configure the second network virtualization deviceto: receive a third packet generated by a second compute instance;determine, based on a second packet flow rule associated with the secondcompute instance, a second network boundary within which packets of thesecond compute instance can flow; determine that a flow of the thirdpacket is within the second network boundary; generate second dataindicating that the flow of the third packet is permitted within thesecond network boundary; include the second data in the third packet;and send, to the first network virtualization device and based on thefirst network virtualization device being within the second networkboundary, the third packet that includes the second data.
 12. Thecomputer system of claim 1, wherein the execution of thecomputer-readable instructions further configures the first networkvirtualization device to: receive, from the second networkvirtualization device, a third packet that includes second dataindicating that the third packet is permitted to flow within a secondnetwork boundary, wherein the second data is included in the thirdpacket based on a second packet flow rule, and wherein the secondnetwork boundary is the same as or different from the network boundary;and enforce the second network boundary by at least determining, basedon the second network boundary, that the third packet is permitted toflow to the compute instance, and sending the third packet to a hostmachine of the compute instance.
 13. A method implemented by a firstnetwork virtualization device, the method comprising: receiving a packetgenerated by a compute instance of a virtual network associated with acustomer; determining, based on a flow packet rule associated with thecompute instance, a network boundary defining a set of one or morenetworks such that a first packet having a destination within thenetwork boundary can flow and such that a second packet having adestination outside of the network boundary is to be dropped;determining that a flow of the packet is within the network boundary;generating data indicating that the flow of the packet is permittedwithin the network boundary; including the data in the packet; andsending, to a second network virtualization device and based on theflow, the packet that includes the data.
 14. The method of claim 13,further comprising: receiving, from the second network virtualizationdevice, a third packet that includes second data indicating that thethird packet is permitted to flow within a second network boundary,wherein the second data is included in the third packet based on asecond packet flow rule, and wherein the second network boundary is thesame as or different from the network boundary; and enforcing the secondnetwork boundary by at least determining that the third packet ispermitted to flow to the compute instance, and sending the third packetto a host machine of the compute instance.
 15. The method of claim 13,further comprising: receiving, from the second network virtualizationdevice, a third packet that includes second data, wherein the seconddata indicates that the third packet is prohibited from flowing withinthe network boundary; and enforcing a second network boundary by atleast determining that a flow of the third packet includes a portionthat is within the network boundary, and dropping, based on the seconddata, the third packet.
 16. The method of claim 13, further comprising:receiving customer data indicating the packet flow rule, the customerdata corresponding to a selection by the customer of the networkboundary from a set of network boundaries, wherein the set of networkboundaries corresponds to at least a layer 2 (L2) virtual local areanetwork (VLAN) within the virtual network, a layer 3 (L3) subnet withinthe virtual network, the virtual network, a private network of thecustomer peered with the virtual network, another virtual network peeredwith the virtual network, and a public network; and generating thepacket flow rule based on the customer data.
 17. One or morenon-transitory computer-readable media storing instructions that, uponexecution on a first network virtualization device, cause the firstnetwork virtualization device to perform operations comprising:receiving, from a second network virtualization device, a first packetthat is generated by a first compute instance of a virtual networkassociated with a customer and that includes first data, wherein thefirst data is included in the first packet based on a packet flow ruleassociated with the first compute instance and indicates that the firstpacket is permitted to flow within a network boundary, the networkboundary defining a set of one or more networks such that a secondpacket having a destination within the network boundary can flow andsuch that a third packet having a destination outside of the networkboundary is to be dropped; determining, based on the first data, thatthe first packet is permitted to flow within the network boundary; andsending the first packet to a third network virtualization device or ahost machine within the network boundary, wherein the host machineexecutes a second compute instance that is a destination of the firstpacket.
 18. The one or more non-transitory computer-readable media ofclaim 17, wherein the operations further comprise: receiving a fourthpacket generated by the second compute instance; determining, based onsecond data included in the fourth packet, that the fourth packet ispermitted to flow within a second network boundary, wherein the seconddata is included in the fourth packet based on a second packet flow ruleassociated with the second compute instance, and wherein the secondnetwork boundary is the same as or different from the network boundary;enforcing the second network boundary by at least determining that thesecond network virtualization device is within the second networkboundary, and sending the fourth packet to the second networkvirtualization device.
 19. The one or more non-transitorycomputer-readable media of claim 17, wherein the operations furthercomprise: receiving, from the second network virtualization device, afourth packet that is generated by the first compute instance and thatincludes second data, wherein the second data is included in the fourthpacket based on the packet flow rule and indicates that the fourthpacket is permitted to flow within the network boundary; and enforcingthe second network boundary by at least determining that a flow of thefourth packet includes a portion that is outside of the networkboundary, and dropping, based on the second data, the fourth packet. 20.The one or more non-transitory computer-readable media of claim 17,wherein the operations further comprise: receiving a fourth packetgenerated by the second compute instance; determining, based on a secondpacket flow rule associated with the second compute instance, a secondnetwork boundary within which packets of the second compute instance canflow; determining that a flow of the fourth packet is within the secondnetwork boundary; generating second data indicating that the flow of thefourth packet is permitted within the second network boundary; includingthe second data in the fourth packet; and sending, to the second networkvirtualization device and based on the second network virtualizationdevice being within the second network boundary, the fourth packet thatincludes the second data.